critical
9.8
CWE
502
Advisory Published
Updated

CVE-2020-5413: Kryo Configuration Allows Code Execution with Unknown "Serialization Gadgets"

First published: Fri Jul 31 2020(Updated: )

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.

Credit: security@pivotal.io

Affected SoftwareAffected VersionHow to fix
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
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
Oracle Banking Credit Facilities Process Management=14.5.0
Oracle Banking Supply Chain Finance=14.2.0
Oracle Banking Supply Chain Finance=14.3.0
Oracle Banking Supply Chain Finance=14.5.0
Oracle Banking Virtual Account Management=14.2.0
Oracle Banking Virtual Account Management=14.3.0
Oracle Banking Virtual Account Management=14.5.0
Oracle FLEXCUBE Private Banking=12.0.0
Oracle FLEXCUBE Private Banking=12.1.0
Oracle Retail Customer Management and Segmentation Foundation>=16.0<=19.0
Oracle Retail Merchandising System=16.0.3

Remedy

https://www.oracle.com//security-alerts/cpujul2021.html

Remedy

https://www.oracle.com/security-alerts/cpuApr2021.html

Remedy

https://www.oracle.com/security-alerts/cpuapr2022.html

Remedy

https://www.oracle.com/security-alerts/cpuoct2021.html

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is vulnerability CVE-2020-5413?

    Vulnerability CVE-2020-5413 is a vulnerability in the Spring Integration framework that allows for deserialization attacks.

  • How does vulnerability CVE-2020-5413 affect VMware Spring Integration?

    Vulnerability CVE-2020-5413 affects VMware Spring Integration versions 4.3.0 to 4.3.22, 5.1.0 to 5.1.11, 5.2.0 to 5.2.7, and 5.3.0 to 5.3.1.

  • How does vulnerability CVE-2020-5413 affect Oracle Banking Corporate Lending Process Management?

    Vulnerability CVE-2020-5413 affects Oracle Banking Corporate Lending Process Management versions 14.2.0, 14.3.0, and 14.5.0.

  • How does vulnerability CVE-2020-5413 affect Oracle Banking Credit Facilities Process Management?

    Vulnerability CVE-2020-5413 affects Oracle Banking Credit Facilities Process Management versions 14.2.0, 14.3.0, and 14.5.0.

  • How does vulnerability CVE-2020-5413 affect Oracle Banking Supply Chain Finance?

    Vulnerability CVE-2020-5413 affects Oracle Banking Supply Chain Finance versions 14.2.0, 14.3.0, and 14.5.0.

  • How does vulnerability CVE-2020-5413 affect Oracle Banking Virtual Account Management?

    Vulnerability CVE-2020-5413 affects Oracle Banking Virtual Account Management versions 14.2.0, 14.3.0, and 14.5.0.

  • How does vulnerability CVE-2020-5413 affect Oracle FLEXCUBE Private Banking?

    Vulnerability CVE-2020-5413 affects Oracle FLEXCUBE Private Banking versions 12.0.0 and 12.1.0.

  • How does vulnerability CVE-2020-5413 affect Oracle Retail Customer Management and Segmentation Foundation?

    Vulnerability CVE-2020-5413 affects Oracle Retail Customer Management and Segmentation Foundation versions 16.0 to 19.0.

  • How does vulnerability CVE-2020-5413 affect Oracle Retail Merchandising System?

    Vulnerability CVE-2020-5413 affects Oracle Retail Merchandising System version 16.0.3.

  • What is the severity of vulnerability CVE-2020-5413?

    Vulnerability CVE-2020-5413 has a severity rating of critical (9.8 out of 10).

  • How can vulnerability CVE-2020-5413 be fixed?

    To fix vulnerability CVE-2020-5413, update to a patched version of the affected software.

  • Where can I find more information about vulnerability CVE-2020-5413?

    For more information about vulnerability CVE-2020-5413, you can refer to the following references: [link1], [link2], [link3].

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203