Open Redirector in spring-security-oauth2
- 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 v2.2.5.RELEASE, v2.1.5.RELEASE, v2.0.18.RELEASE, v2.3.6.RELEASE, 2.0.18.RELEASE, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 on Exploit-DB
Summary
Spring Security OAuth versions 2.3 prior to 2.3.6, 2.2 prior to 2.2.5, 2.1 prior to 2.1.5, and 2.0 prior to 2.0.18, as well as older unsupported versions could be susceptible to an open redirector attack that can leak an authorization code. A malicious user or attacker can craft a request to the authorization endpoint using the authorization code grant type, and specify a manipulated redirection URI via the redirect_uri parameter. This can cause the authorization server to redirect the resource owner user-agent to a URI under the control of the attacker with the leaked authorization code.
Timeline
- CVE published
- Public exploit on Exploit-DB
EDB-47000
- Record last updated
Affected versions
- Spring Spring Security OAuth
From 2.2 · fixed in v2.2.5.RELEASE; From 2.1 · fixed in v2.1.5.RELEASE; From 2.0 · fixed in v2.0.18.RELEASE; From 2.3 · fixed in v2.3.6.RELEASE
- org.springframework.security.oauth:spring-security-oauthMaven
From 2.0.0.RELEASE · fixed in 2.0.18.RELEASE
- org.springframework.security.oauth:spring-security-oauthMaven
From 2.1.0.RELEASE · fixed in 2.1.5.RELEASE
- org.springframework.security.oauth:spring-security-oauthMaven
From 2.2.0.RELEASE · fixed in 2.2.5.RELEASE
- org.springframework.security.oauth:spring-security-oauthMaven
From 2.3.0.RELEASE · fixed in 2.3.6.RELEASE