CVE-2016-4977GHSA-7Q9C-H23X-65FQ
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_t
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.0.10, 1.0.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 3 proofs of concept on GitHub, 1 Nuclei template
Summary
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.
Timeline
- CVE published
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Pivotal Spring Security OAuth
2.0.0 to 2.0.9, 1.0.0 to 1.0.5
- org.springframework.security.oauth:spring-security-oauth2Maven
From 2.0.0 · fixed in 2.0.10
- org.springframework.security.oauth:spring-security-oauth2Maven
From 1.0.0 · fixed in 1.0.5
References 10
pivotal.io
lists.apache.org
- thread.html/37d7e820fc65a768de3e096e98382d5529a52a039f093e59357d0bc0@<dev.fineract.apache.org>
- thread.html/0841d849c23418c473ccb9183cbf41a317cb0476e44be48022ce3488@<dev.fineract.apache.org>
- thread.html/5e6dd946635bbcc9e1f2591599ad0fab54f2dc3714196af3b17893f2@<announce.apache.org>
- thread.html/96c017115069408cec5e82ce1e6293facab398011f6db7e1befbe274@<dev.fineract.apache.org>