CVE-2016-4977

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.

Category

8.8
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 94.16% Top 5%
Vendor Advisory pivotal.io
Affected: Pivotal Spring Security OAuth
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2016-4977?
CVE-2016-4977 has been scored as a high severity vulnerability.
How to fix CVE-2016-4977?
To fix CVE-2016-4977, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-4977 being actively exploited in the wild?
It is possible that CVE-2016-4977 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~94% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2016-4977?
CVE-2016-4977 affects Pivotal Spring Security OAuth.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.