critical
9.8
CWE
502
Advisory Published
Advisory Published
Updated

CVE-2017-4995

First published: Mon Nov 27 2017(Updated: )

An issue was discovered in Pivotal Spring Security 4.2.0.RELEASE through 4.2.2.RELEASE, and Spring Security 5.0.0.M1. When configured to enable default typing, Jackson contained a deserialization vulnerability that could lead to arbitrary code execution. Jackson fixed this vulnerability by blacklisting known "deserialization gadgets." Spring Security configures Jackson with global default typing enabled, which means that (through the previous exploit) arbitrary code could be executed if all of the following is true: (1) Spring Security's Jackson support is being leveraged by invoking SecurityJackson2Modules.getModules(ClassLoader) or SecurityJackson2Modules.enableDefaultTyping(ObjectMapper); (2) Jackson is used to deserialize data that is not trusted (Spring Security does not perform deserialization using Jackson, so this is an explicit choice of the user); and (3) there is an unknown (Jackson is not blacklisting it already) "deserialization gadget" that allows code execution present on the classpath. Jackson provides a blacklisting approach to protecting against this type of attack, but Spring Security should be proactive against blocking unknown "deserialization gadgets" when Spring Security enables default typing.

Credit: security_alert@emc.com security_alert@emc.com

Affected SoftwareAffected VersionHow to fix
Vmware Spring Security=4.2.0-release
Vmware Spring Security=4.2.1-release
Vmware Spring Security=4.2.2-release
Vmware Spring Security=5.0.0-m1
IBM GDE<=3.0.0.2
maven/org.springframework.security:spring-security-core>=4.2.0.RELEASE<=4.2.2.RELEASE
4.2.3.RELEASE
maven/org.springframework.security:spring-security-core=5.0.0.M1
5.0.0.M2
=4.2.0-release
=4.2.1-release
=4.2.2-release
=5.0.0-m1

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

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is CVE-2017-4995?

    CVE-2017-4995 is a vulnerability in Pivotal Spring Security and Spring Security that allows a remote attacker to execute arbitrary code on the system.

  • How does the CVE-2017-4995 vulnerability occur?

    The CVE-2017-4995 vulnerability occurs due to a deserialization vulnerability in Jackson when configured to enable default typing.

  • What is the severity rating of CVE-2017-4995?

    CVE-2017-4995 has a severity rating of 9.8 (Critical).

  • Which software versions are affected by CVE-2017-4995?

    Pivotal Spring Security versions 4.2.0.RELEASE through 4.2.2.RELEASE and Spring Security version 5.0.0.M1 are affected by CVE-2017-4995.

  • How can I fix the CVE-2017-4995 vulnerability?

    To fix the CVE-2017-4995 vulnerability, update Pivotal Spring Security to version 4.2.3.RELEASE or later, or update Spring Security to version 5.0.0.M2 or later.

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