Open Redirector in spring-security-oauth2
Spring Security OAuth
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security.oauth:spring-security-oauth Maven |
|
|
Spring Security OAuth
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security.oauth:spring-security-oauth Maven |
|
|
2.3.6.RELEASESpring 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.
From the CVE record · pivotal
Affected Spring Security OAuth versions can allow an open redirect that leaks an authorization code. An attacker can craft an authorization-code grant request with a manipulated redirect_uri, causing the authorization server to redirect the resource owner's user-agent to an attacker-controlled URI with the code.
Teams using the Maven package org.springframework.security.oauth:spring-security-oauth should check 2.0.0.RELEASE through versions before 2.0.18.RELEASE, 2.1.0.RELEASE through versions before 2.1.5.RELEASE, 2.2.0.RELEASE through versions before 2.2.5.RELEASE, and 2.3.0.RELEASE through versions before 2.3.6.RELEASE, as well as older unsupported versions.