Tracker / CVE-2020-5413
CVE-2020-5413
Critical 9.8
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.
Affected products and versions
| oracle | banking_corporate_lending_process_management |
|---|---|
| oracle | banking_credit_facilities_process_management |
| oracle | banking_supply_chain_finance |
| oracle | banking_virtual_account_management |
| oracle | flexcube_private_banking |
| oracle | retail_customer_management_and_segmentation_foundation · 16.0 → 19.0 |
| oracle | retail_merchandising_system |
| vmware | spring_integration · 4.3.0 → 4.3.22 |
| vmware | spring_integration · 5.1.0 → 5.1.11 |
| vmware | spring_integration · 5.2.0 → 5.2.7 |
| vmware | spring_integration · 5.3.0 → 5.3.1 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.