Skip to content

spring-security-oauth and spring-security-oauth2 Open Redirect vulnerability

Moderate severity GitHub Reviewed Published Mar 14, 2019 to the GitHub Advisory Database • Updated Jun 20, 2023

Package

maven org.springframework.security.oauth:spring-security-oauth (Maven)

Affected versions

< 2.0.17.RELEASE
>= 2.1.0.RELEASE, < 2.1.4.RELEASE
>= 2.2.0.RELEASE, < 2.2.4.RELEASE
>= 2.3.0.RELEASE, < 2.3.5.RELEASE

Patched versions

2.0.17.RELEASE
2.1.4.RELEASE
2.2.4.RELEASE
2.3.5.RELEASE
maven org.springframework.security.oauth:spring-security-oauth2 (Maven)
< 2.0.17.RELEASE
>= 2.1.0.RELEASE, < 2.1.4.RELEASE
>= 2.2.0.RELEASE, < 2.2.4.RELEASE
>= 2.3.0.RELEASE, < 2.3.5.RELEASE
2.0.17.RELEASE
2.1.4.RELEASE
2.2.4.RELEASE
2.3.5.RELEASE

Description

Spring Security OAuth, versions 2.3 prior to 2.3.5, and 2.2 prior to 2.2.4, and 2.1 prior to 2.1.4, and 2.0 prior to 2.0.17, and 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: Act in the role of an Authorization Server (e.g. @EnableAuthorizationServer) and uses the DefaultRedirectResolver in the AuthorizationEndpoint.

This vulnerability does not expose applications that: Act in the role of an Authorization Server and uses a different RedirectResolver implementation other than DefaultRedirectResolver, act in the role of a Resource Server only (e.g. @EnableResourceServer), act in the role of a Client only (e.g. @EnableOAuthClient).

References

Published by the National Vulnerability Database Mar 7, 2019
Published to the GitHub Advisory Database Mar 14, 2019
Reviewed Jun 16, 2020
Last updated Jun 20, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.439%
(75th percentile)

Weaknesses

CVE ID

CVE-2019-3778

GHSA ID

GHSA-77rv-6vfw-x4gc

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.