CVE intelligence and bounded remediation
CVE-2020-5413 — Spring Integration framework provides Kryo Codec implementations as an alternative for Java (de)serialization
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.
- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Published
- 2020-07-31
- CISA KEV
- Not currently listed
- Ecosystem
- java/maven
- Weaknesses
- CWE-502
Affected products
- 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
Showing 6 representative product identities from 20 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.
Matched remediation archetype
Unsafe deserialization and object reconstruction
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory serialization formats accepted from requests, queues, caches, files, cookies, and cross-service messages.
- Trace whether untrusted input can select classes, types, callbacks, constructors, or object hooks during decoding.
- Identify signing, schema validation, trust-boundary, and compatibility settings for each decoder.
Remediate safely
- Replace native object deserialization with a data-only format and explicit schema validation.
- If replacement is not immediate, use a safe decoder with a minimal type allowlist and disable polymorphic or executable hooks.
- Update the affected library and add inert tests for unknown types, extra fields, malformed nesting, and unsigned data.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.