CVE-2019-3778 Open Redirect in spring-security-oauth2
Attackers can exploit an open redirect in Spring Security OAuth to leak authorization codes, potentially leading to account takeover.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2019-3778?
CVE-2019-3778 is a medium-severity vulnerability in Spring Security OAuth, published on 7 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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).
Weakness: CWE-601
Which versions are affected by CVE-2019-3778?
16 open source packages ship an affected version, including org.springframework.security.oauth:spring-security-oauth and org.springframework.security.oauth:spring-security-oauth2. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
org.springframework.security.oauth:spring-security-oauth Maven | All versions | 2.0.17.RELEASE |
org.springframework.security.oauth:spring-security-oauth Maven | All versions | 2.0.17.RELEASE |
org.springframework.security.oauth:spring-security-oauth Maven | From 2.1.0.RELEASE | 2.1.4.RELEASE |
org.springframework.security.oauth:spring-security-oauth Maven | From 2.1.0.RELEASE | 2.1.4.RELEASE |
org.springframework.security.oauth:spring-security-oauth Maven | From 2.2.0.RELEASE | 2.2.4.RELEASE |
org.springframework.security.oauth:spring-security-oauth Maven | From 2.2.0.RELEASE | 2.2.4.RELEASE |
10 more packages
org.springframework.security.oauth:spring-security-oauth Maven | From 2.3.0.RELEASE | 2.3.5.RELEASE |
org.springframework.security.oauth:spring-security-oauth Maven | From 2.3.0.RELEASE | 2.3.5.RELEASE |
org.springframework.security.oauth:spring-security-oauth2 Maven | All versions | 2.0.17.RELEASE |
org.springframework.security.oauth:spring-security-oauth2 Maven | All versions | 2.0.17.RELEASE |
org.springframework.security.oauth:spring-security-oauth2 Maven | From 2.1.0.RELEASE | 2.1.4.RELEASE |
org.springframework.security.oauth:spring-security-oauth2 Maven | From 2.1.0.RELEASE | 2.1.4.RELEASE |
org.springframework.security.oauth:spring-security-oauth2 Maven | From 2.2.0.RELEASE | 2.2.4.RELEASE |
org.springframework.security.oauth:spring-security-oauth2 Maven | From 2.2.0.RELEASE | 2.2.4.RELEASE |
org.springframework.security.oauth:spring-security-oauth2 Maven | From 2.3.0.RELEASE | 2.3.5.RELEASE |
org.springframework.security.oauth:spring-security-oauth2 Maven | From 2.3.0.RELEASE | 2.3.5.RELEASE |
Products include Oracle Banking Corporate Lending, Pivotal Software Spring Security Oauth.
How do I fix CVE-2019-3778?
Upgrade org.springframework.security.oauth:spring-security-oauth to a fixed version for your release line: 2.0.17.RELEASE, 2.1.4.RELEASE, 2.2.4.RELEASE or 2.3.5.RELEASE.
Is CVE-2019-3778 being exploited?
There is no known exploitation of CVE-2019-3778 in the wild and no public exploit code.
Public exploit code: 1 Exploit-DB entry and 1 proofs of concept on GitHub.
Other vulnerabilities in Spring Security OAuth
- CVE-2018-2706 Auth bypass in Banking Corporate Lending
- CVE-2018-3050 Missing authorization in Banking Corporate Lending
- CVE-2018-2707 Missing authorization in Banking Corporate Lending
- CVE-2020-2718 Missing authorization in Banking Corporate Lending
- CVE-2018-2746 Information disclosure in FLEXCUBE Universal Banking
Sources
Also known as GHSA-77rv-6vfw-x4gc.