Strix
26.1K

CVE-2016-4977

UnknownEPSS 79.18%

Last modified

CVE-2016-4977 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 79.18% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
79.18%

99.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
PivotalSpring Security Oauth1.0.0
PivotalSpring Security Oauth1.0.1
PivotalSpring Security Oauth1.0.2
PivotalSpring Security Oauth1.0.3
PivotalSpring Security Oauth1.0.4
PivotalSpring Security Oauth1.0.5
PivotalSpring Security Oauth2.0.0
PivotalSpring Security Oauth2.0.1
PivotalSpring Security Oauth2.0.2
PivotalSpring Security Oauth2.0.3
PivotalSpring Security Oauth2.0.4
PivotalSpring Security Oauth2.0.5
PivotalSpring Security Oauth2.0.6
PivotalSpring Security Oauth2.0.7
PivotalSpring Security Oauth2.0.8
PivotalSpring Security Oauth2.0.9

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-4977?
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.
How severe is CVE-2016-4977?
Severity scoring for CVE-2016-4977 is pending analysis. The EPSS model estimates a 79.18% probability of exploitation in the next 30 days.
How do I fix CVE-2016-4977?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-4977?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST