CVE-2019-3778

Open Redirect in spring-security-oauth2

MEDIUM
6.5
CVSS Score
Published: March 7, 2019 at 07:00 PM UTC
Updated: June 17, 2026 at 02:35 AM UTC
3 products affected across 3 vendorsBanking Corporate LendingSpring Security OAuthSpring Security OAuth

Using Spring Security OAuth by Spring?

Get instant alerts when new vulnerabilities affect Spring Security OAuth - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 17%

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).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.0.0 ≤ v < 2.0.172.1.0 ≤ v < 2.1.42.2.0 ≤ v < 2.2.42.3.0 ≤ v < 2.3.5
Affected range stops below 2.0.17, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.2.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.5, so it looks safe — our inference, not a vendor statement
2.0 ≤ v < 2.0.17.RELEASE2.1 ≤ v < 2.1.4.RELEASE2.2 ≤ v < 2.2.4.RELEASE2.3 ≤ v < 2.3.5.RELEASE2.02.12.22.3
Affected range stops below 2.0.17.RELEASE, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.1.4.RELEASE, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.2.4.RELEASE, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.5.RELEASE, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (4)

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-601

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card