CVE-2019-3778 — spring-security-oauth
MEDIUMCVE-2019-3778 is a medium-severity (CVSS 6.5) Open Redirect vulnerability in org.springframework.security.oauth:spring-security-oauth. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.springframework.security.oauth:spring-security-oauth — see the affected versions and patch details below.
spring-security-oauth and spring-security-oauth2 Open Redirect vulnerability
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.security.oauth:spring-security-oauth☕org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth☕org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth☕org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth☕org.springframework.security.oauth:spring-security-oauth2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security.oauth:spring-security-oauth | all versions | 2.0.17.RELEASEorg.springframework.security.oauth:spring-security-oauth:2.0.17.RELEASE |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | all versions | 2.0.17.RELEASEorg.springframework.security.oauth:spring-security-oauth2:2.0.17.RELEASE |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth | ≥ 2.1.0.RELEASE&&< 2.1.4.RELEASE | 2.1.4.RELEASEorg.springframework.security.oauth:spring-security-oauth:2.1.4.RELEASE |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.1.0.RELEASE&&< 2.1.4.RELEASE | 2.1.4.RELEASEorg.springframework.security.oauth:spring-security-oauth2:2.1.4.RELEASE |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth | ≥ 2.2.0.RELEASE&&< 2.2.4.RELEASE | 2.2.4.RELEASEorg.springframework.security.oauth:spring-security-oauth:2.2.4.RELEASE |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.2.0.RELEASE&&< 2.2.4.RELEASE | 2.2.4.RELEASEorg.springframework.security.oauth:spring-security-oauth2:2.2.4.RELEASE |
Affected Products
banking corporate lendingoraclespring security oauthpivotal_softwareResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Spring Security OAuth - Open Redirector
by Riemann · Jun 17, 2019
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security.oauth:spring-security-oauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.security.oauth:spring-security-oauth to 2.0.17.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3778 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Frequently Asked Questions
Is CVE-2019-3778 in your dependencies?
Find it across Maven, including transitive dependencies.