high
8.8
CWE
19
Advisory Published
Advisory Published
Updated

CVE-2016-4977

First published: Thu May 25 2017(Updated: )

When processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to 1.0.5, the response_type parameter value was executed as Spring SpEL which enabled a malicious user to trigger remote code execution via the crafting of the value for response_type.

Credit: security_alert@emc.com

Affected SoftwareAffected VersionHow to fix
maven/org.springframework.security.oauth:spring-security-oauth2>=1.0.0<1.0.5
1.0.5
maven/org.springframework.security.oauth:spring-security-oauth2>=2.0.0<2.0.10
2.0.10
Pivotal Software Spring Security=1.0.0
Pivotal Software Spring Security=1.0.1
Pivotal Software Spring Security=1.0.2
Pivotal Software Spring Security=1.0.3
Pivotal Software Spring Security=1.0.4
Pivotal Software Spring Security=1.0.5
Pivotal Software Spring Security=2.0.0
Pivotal Software Spring Security=2.0.1
Pivotal Software Spring Security=2.0.2
Pivotal Software Spring Security=2.0.3
Pivotal Software Spring Security=2.0.4
Pivotal Software Spring Security=2.0.5
Pivotal Software Spring Security=2.0.6
Pivotal Software Spring Security=2.0.7
Pivotal Software Spring Security=2.0.8
Pivotal Software Spring Security=2.0.9

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 the severity of CVE-2016-4977?

    CVE-2016-4977 is classified as a critical vulnerability due to its potential for remote code execution.

  • How do I fix CVE-2016-4977?

    To mitigate CVE-2016-4977, upgrade to Spring Security OAuth version 1.0.6 or 2.0.10 or later.

  • What are the affected versions in CVE-2016-4977?

    CVE-2016-4977 affects Spring Security OAuth versions from 1.0.0 to 1.0.5 and from 2.0.0 to 2.0.9.

  • What is the primary risk associated with CVE-2016-4977?

    The primary risk associated with CVE-2016-4977 is the ability for attackers to execute arbitrary code on the server.

  • Can CVE-2016-4977 be exploited without user interaction?

    Yes, CVE-2016-4977 can be exploited remotely without the need for user interaction.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203