CVE-2016-4977
HighExploitedSpring Security OAuth vulnerable to remote code execution (RCE) via specially crafted request using whitelabel views
Published Oct 18, 2018 · Updated Aug 27, 2026 · Also known as GHSA-7q9c-h23x-65fq
Key Facts
Patch immediately- CVE-2016-4977 is a high-severity vulnerability (CVSS 8.8 v3.1) affecting Spring Security OAuth (Pivotal), org.springframework.security.oauth:spring-security-oauth2 (maven).
- It is exploited in the wild, listed in Industry KEV feed since Aug 14, 2024. No public exploit code is known.
- EPSS estimates a 79% probability of exploitation in the next 30 days.
- Fixed versions are available, including org.springframework.security.oauth:spring-security-oauth2 1.0.5, org.springframework.security.oauth:spring-security-oauth2 2.0.10.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
8.8
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
79%
Higher than 99.5% of all scored CVEs
Exploited in the wild
Yes
1 catalog listing
Public exploit code
None known
Get the full CVE-2016-4977 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| Industry KEV feed | Aug 14, 2024 | n/a | Not reported |
Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected Products
18 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Spring Security OAuthPivotal | 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 2.0.0, 2.0.1 | n/a |
| org.springframework.security.oauth:spring-security-oauth2maven | >= 2.0.0 | 1.0.5 |
Patched Releases
org.springframework.security.oauth:spring-security-oauth2
1.0.5, 2.0.10
Timeline
Publicly disclosed
Oct 18, 2018
Added to Industry KEV feed
Aug 14, 2024
Last updated
Aug 27, 2026
Weakness Type
- CWE-19
References
- advisoryGHSA advisory
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2016-4977
- exploitVulnCheck exploitation report
- articlehttps://lists.apache.org/thread.html/0841d849c23418c473ccb9183cbf41a317cb0476e44be48022ce3488@%3Cdev.fineract.apache.org%3E
- articlehttps://lists.apache.org/thread.html/37d7e820fc65a768de3e096e98382d5529a52a039f093e59357d0bc0@%3Cdev.fineract.apache.org%3E
FAQ
Common Questions.
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.
Affected: Spring Security OAuth (Pivotal) versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 2.0.0, 2.0.1; org.springframework.security.oauth:spring-security-oauth2 (maven) versions >= 2.0.0. The full list is in the CVE brief.
It is exploited in the wild, listed in Industry KEV feed since Aug 14, 2024.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including org.springframework.security.oauth:spring-security-oauth2 1.0.5, org.springframework.security.oauth:spring-security-oauth2 2.0.10.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2016-4977 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo