What is CVE-2019-3778?

CVE-2019-3778 is a medium-severity open redirect vulnerability in org.springframework.security.oauth:spring-security-oauth (maven), affecting versions < 2.0.17.RELEASE. It is fixed in 2.0.17.RELEASE, 2.1.4.RELEASE, 2.2.4.RELEASE, 2.3.5.RELEASE. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.

How severe is CVE-2019-3778?

CVE-2019-3778 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2019-3778?

org.springframework.security.oauth:spring-security-oauth (maven) versions < 2.0.17.RELEASE; org.springframework.security.oauth:spring-security-oauth2 (maven) versions < 2.0.17.RELEASE.

Is CVE-2019-3778 exploitable, and should I be worried?

Whether CVE-2019-3778 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-3778 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2019-3778

Q: How severe is CVE-2019-3778?

CVE-2019-3778 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Is there a fix for CVE-2019-3778?

Yes. CVE-2019-3778 is fixed in 2.0.17.RELEASE, 2.1.4.RELEASE, 2.2.4.RELEASE, 2.3.5.RELEASE. Upgrade to this version or later.

Q: Is CVE-2019-3778 exploitable, and should I be worried?

Whether CVE-2019-3778 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-3778 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-3778?

Upgrade: org.springframework.security.oauth:spring-security-oauth to 2.0.17.RELEASE or later, org.springframework.security.oauth:spring-security-oauth2 to 2.0.17.RELEASE or later, org.springframework.security.oauth:spring-security-oauth to 2.1.4.RELEASE or later, org.springframework.security.oauth:spring-security-oauth2 to 2.1.4.RELEASE or later, org.springframework.security.oauth:spring-security-oauth to 2.2.4.RELEASE or later, org.springframework.security.oauth:spring-security-oauth2 to 2.2.4.RELEASE or later, org.springframework.security.oauth:spring-security-oauth to 2.3.5.RELEASE or later, org.springframework.security.oauth:spring-security-oauth2 to 2.3.5.RELEASE or later.

Summary

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

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

Impact

Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.

CVE-2019-3778 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.17.RELEASE, 2.1.4.RELEASE, 2.2.4.RELEASE, 2.3.5.RELEASE); upgrading removes the vulnerable code path.

Affected versions

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

Security releases

org.springframework.security.oauth:spring-security-oauth → 2.0.17.RELEASE (maven) org.springframework.security.oauth:spring-security-oauth2 → 2.0.17.RELEASE (maven) org.springframework.security.oauth:spring-security-oauth → 2.1.4.RELEASE (maven) org.springframework.security.oauth:spring-security-oauth2 → 2.1.4.RELEASE (maven) org.springframework.security.oauth:spring-security-oauth → 2.2.4.RELEASE (maven) org.springframework.security.oauth:spring-security-oauth2 → 2.2.4.RELEASE (maven) org.springframework.security.oauth:spring-security-oauth → 2.3.5.RELEASE (maven) org.springframework.security.oauth:spring-security-oauth2 → 2.3.5.RELEASE (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.springframework.security.oauth:spring-security-oauth to 2.0.17.RELEASE or later; org.springframework.security.oauth:spring-security-oauth2 to 2.0.17.RELEASE or later; org.springframework.security.oauth:spring-security-oauth to 2.1.4.RELEASE or later; org.springframework.security.oauth:spring-security-oauth2 to 2.1.4.RELEASE or later; org.springframework.security.oauth:spring-security-oauth to 2.2.4.RELEASE or later; org.springframework.security.oauth:spring-security-oauth2 to 2.2.4.RELEASE or later; org.springframework.security.oauth:spring-security-oauth to 2.3.5.RELEASE or later; org.springframework.security.oauth:spring-security-oauth2 to 2.3.5.RELEASE or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2019-3778? CVE-2019-3778 is a medium-severity open redirect vulnerability in org.springframework.security.oauth:spring-security-oauth (maven), affecting versions < 2.0.17.RELEASE. It is fixed in 2.0.17.RELEASE, 2.1.4.RELEASE, 2.2.4.RELEASE, 2.3.5.RELEASE. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
How severe is CVE-2019-3778? CVE-2019-3778 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2019-3778?
- org.springframework.security.oauth:spring-security-oauth (maven) (versions < 2.0.17.RELEASE)
- org.springframework.security.oauth:spring-security-oauth2 (maven) (versions < 2.0.17.RELEASE)
Is there a fix for CVE-2019-3778? Yes. CVE-2019-3778 is fixed in 2.0.17.RELEASE, 2.1.4.RELEASE, 2.2.4.RELEASE, 2.3.5.RELEASE. Upgrade to this version or later.
Is CVE-2019-3778 exploitable, and should I be worried? Whether CVE-2019-3778 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-3778 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-3778?
- Upgrade org.springframework.security.oauth:spring-security-oauth to 2.0.17.RELEASE or later
- Upgrade org.springframework.security.oauth:spring-security-oauth2 to 2.0.17.RELEASE or later
- Upgrade org.springframework.security.oauth:spring-security-oauth to 2.1.4.RELEASE or later
- Upgrade org.springframework.security.oauth:spring-security-oauth2 to 2.1.4.RELEASE or later
- Upgrade org.springframework.security.oauth:spring-security-oauth to 2.2.4.RELEASE or later
- Upgrade org.springframework.security.oauth:spring-security-oauth2 to 2.2.4.RELEASE or later
- Upgrade org.springframework.security.oauth:spring-security-oauth to 2.3.5.RELEASE or later
- Upgrade org.springframework.security.oauth:spring-security-oauth2 to 2.3.5.RELEASE or later

Other vulnerabilities in org.springframework.security.oauth:spring-security-oauth

CVE-IDSeverityPackage summary

CVE-2019-11269Mediumorg.springframework.security.oauth:spring-security-oauth: Open Redirect in Spring Security OAuth