Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreSpring 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.
This vulnerability exposes applications that meet all of the following requirements:
@EnableAuthorizationServer
)DefaultRedirectResolver
in the AuthorizationEndpoint
This vulnerability does not expose applications that:
RedirectResolver
implementation other than DefaultRedirectResolver
@EnableResourceServer
)@EnableOAuthClient
)Users of affected versions should apply the following mitigation:
There are no other mitigation steps necessary.
For users of Spring Boot 1.5.x and Spring IO Platform Cairo, it is highly recommended to override the spring-security-oauth
version to the latest version containing the patch for the CVE. In order to override the version, you need to declare/set the property spring-security-oauth.version
.
Below are instructions for users of Spring Boot 1.5.x.
To override a property using Maven, declare the property in your pom’s
section:
To override a property using Gradle, configure the value in your build.gradle script:
ext['spring-security-oauth.version'] = '2.0.18.RELEASE'
Or in gradle.properties:
spring-security-oauth.version=2.0.18.RELEASE
NOTE: The same instructions apply for users of Spring IO Platform Cairo. However, the version to specify is 2.2.5.RELEASE.
This issue was identified and responsibly reported by Mike Noordermeer.
2019-05-30: Initial vulnerability report published
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy