Spring Security OAuth up to 2.0.16/2.1.3/2.2.3/2.3.4 Authorization Endpoint redirect_uri

Summaryinfo

A vulnerability labeled as problematic has been found in Spring Security OAuth up to 2.0.16/2.1.3/2.2.3/2.3.4. The affected element is an unknown function of the component Authorization Endpoint. Such manipulation of the argument redirect_uri leads to redirect. This vulnerability is documented as CVE-2019-3778. The attack can be executed remotely. Additionally, an exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Spring Security OAuth up to 2.0.16/2.1.3/2.2.3/2.3.4. Affected by this issue is an unknown part of the component Authorization Endpoint. The manipulation of the argument redirect_uri with an unknown input leads to a redirect vulnerability. Using CWE to declare the problem leads to CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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

The bug was discovered 02/21/2019. The weakness was released 03/07/2019 (Website). The advisory is shared for download at pivotal.io. This vulnerability is handled as CVE-2019-3778 since 01/03/2019. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1204.001.

The exploit is available at packetstormsecurity.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 14 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 2.0.17, 2.1.4, 2.2.4 or 2.3.5 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Exploit-DB (47000). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

• Spring Security OAuth

Version

• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 2.0.10
• 2.0.11
• 2.0.12
• 2.0.13
• 2.0.14
• 2.0.15
• 2.0.16
• 2.1.0
• 2.1.1
• 2.1.2
• 2.1.3
• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.3.0
• 2.3.1
• 2.3.2
• 2.3.3
• 2.3.4

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion