CVE-2020-5413
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.
Published:Jul 31, 2020
Last Modified:Nov 21, 2024
EPS:Jul 31, 2020
EPSS Score:0.02178
CVSS Score:9.8
Affected Products
Vendor
Product
Action
Vendor
Oracle
Product
Banking Corporate Lending Process Management
Oracle
Banking Corporate Lending Process Management
Vendor
Oracle
Product
Banking Credit Facilities Process Management
Oracle
Banking Credit Facilities Process Management
Vendor
Oracle
Product
Banking Supply Chain Finance
Oracle
Banking Supply Chain Finance
Vendor
Oracle
Product
Banking Virtual Account Management
Oracle
Banking Virtual Account Management
Vendor
Oracle
Product
Flexcube Private Banking
Oracle
Flexcube Private Banking
Vendor
Oracle
Product
Retail Customer Management And Segmentation Foundation
Oracle
Retail Customer Management And Segmentation Foundation
Vendor
Oracle
Product
Retail Merchandising System
Oracle
Retail Merchandising System
Vendor
Vmware
Product
Spring Integration
Vmware
Spring Integration
Exploits
No exploit reference
Common Weakness Enumeration
Common Attack Pattern Enumeration and Classification (CAPEC)
Related CVEs
References
Common Vulnerability Scoring System
Attack Vector
Network
Adjacent
Local
Physical
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
