Deserialization in Oracle Banking Corporate Lending Process Management

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.

Vulnerability class: Insecure Deserialization

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.044 (91.3th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 91st percentile — 91.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2020-5413: held from 0.044 to 0.044.

EPSS over last 30 days · oldest: 0.044 · newest: 0.044 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2020-5413?
CVE-2020-5413 is a critical-severity vulnerability in Oracle Banking Corporate Lending Process Management, classified under Deserialization of Untrusted Data. CVSS score: 9.8/10. Published 2020-07-31.
How severe is CVE-2020-5413?
Critical severity. CVSS v3 base score is 9.8 out of 10.
Is CVE-2020-5413 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.