Impact
SOFARPC defaults to using the SOFA Hessian protocol to deserialize received data, while the SOFA Hessian protocol uses a blacklist mechanism to restrict deserialization of potentially dangerous classes for security protection. But there is a gadget chain that can bypass the SOFA Hessian blacklist protection mechanism, and this gadget chain only relies on JDK and does not rely on any third-party components.
Patches
Fixed this issue by adding a blacklist, users can upgrade to sofarpc version 5.11.1 to avoid this issue.
Workarounds
SOFARPC also provides a way to add additional blacklist. Users can add -Drpc_serialize_blacklist_override=javax.swing. to avoid this issue.
Impact
SOFARPC defaults to using the SOFA Hessian protocol to deserialize received data, while the SOFA Hessian protocol uses a blacklist mechanism to restrict deserialization of potentially dangerous classes for security protection. But there is a gadget chain that can bypass the SOFA Hessian blacklist protection mechanism, and this gadget chain only relies on JDK and does not rely on any third-party components.
Patches
Fixed this issue by adding a blacklist, users can upgrade to sofarpc version 5.11.1 to avoid this issue.
Workarounds
SOFARPC also provides a way to add additional blacklist. Users can add
-Drpc_serialize_blacklist_override=javax.swing.to avoid this issue.