Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization. When Kryo is configured with default options, all unregistered classes are resolved on demand. This leads to the "deserialization gadgets" exploit when provided data contains malicious code for execution during deserialization. In order to protect against this type of attack, Kryo can be configured to require a set of trusted classes for (de)serialization. Spring Integration should be proactive against blocking unknown "deserialization gadgets" when configuring Kryo in code.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
vmware spring integration |
||
oracle banking corporate lending process management 14.2.0 |
||
oracle banking corporate lending process management 14.3.0 |
||
oracle banking corporate lending process management 14.5.0 |
||
oracle banking credit facilities process management 14.2.0 |
||
oracle banking credit facilities process management 14.3.0 |
||
oracle banking credit facilities process management 14.5.0 |
||
oracle banking supply chain finance 14.2.0 |
||
oracle banking supply chain finance 14.3.0 |
||
oracle banking supply chain finance 14.5.0 |
||
oracle banking virtual account management 14.2.0 |
||
oracle banking virtual account management 14.3.0 |
||
oracle banking virtual account management 14.5.0 |
||
oracle flexcube private banking 12.0.0 |
||
oracle flexcube private banking 12.1.0 |
||
oracle retail customer management and segmentation foundation |
||
oracle retail merchandising system 16.0.3 |
Vulmon