Open Redirect in Spring Security OAuth
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.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.springframework.security.oauth:spring-security-oauth | >= 2.0.0.RELEASE, < 2.0.18.RELEASE, >= 2.1.0.RELEASE, < 2.1.5.RELEASE, >= 2.2.0.RELEASE, < 2.2.5.RELEASE, >= 2.3.0.RELEASE, < 2.3.6.RELEASE | 2.0.18.RELEASE, 2.1.5.RELEASE, 2.2.5.RELEASE, 2.3.6.RELEASE |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N- Weakness (CWE)
CWE-601- Platform
- Java / Kotlin (Maven)
- Package
org.springframework.security.oauth:spring-security-oauth- Disclosed
- 13.06.2019
- Updated
- 11.10.2026 12:21
Sources and licenses
OSV / GitHub Advisory Database - GHSA-mmf6-6597-3v6m - CC BY 4.0
Vulnerability history: org.springframework.security.oauth:spring-security-oauth
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 2
- First → latest
- 03.2019 06.2019
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Medium 2
Disclosures per year
- 2019: 2
- 2020: 0
- 2021: 0
- 2022: 0
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 0
-
Open Redirect in Spring Security OAuth this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.