CVE-2019-3778 — spring-security-oauth
MEDIUMCVE-2019-3778 is a medium-severity (CVSS 6.5) vulnerability in org.springframework.security.oauth:spring-security-oauth. 1 public exploit reference exists, 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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2019-3778 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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 |
Research 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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-3778 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-3778. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-3778 in your dependencies?
O3 Security finds CVE-2019-3778 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.