vmware spring-integration CVE-2020-5413 in VMware and Oracle Products
Published on July 31, 2020

Kryo Configuration Allows Code Execution with Unknown "Serialization Gadgets"

product logo product logo
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.

NVD

Weakness Type

What is a Marshaling, Unmarshaling Vulnerability?

The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.

CVE-2020-5413 has been classified to as a Marshaling, Unmarshaling vulnerability or weakness.


Products Associated with CVE-2020-5413

You can be notified by email with stack.watch whenever vulnerabilities like CVE-2020-5413 are published in these products:

 
 
 
 
 
 
 
 

Affected Versions

Spring by VMware Spring Integration:

Exploit Probability

EPSS
2.18%
Percentile
84.07%

EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.