Open Redirect in spring-security-oauth2
28Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendepss 15%
from disclosure to weapon102 days
Published on NVDMar 7
1st PoC+102d
exploitation probability
15%top 4% of all CVEs
observed exploitation
nono source reports it
3 public exploit(s)
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 products
Spring · Spring Security OAuthpublic PoCs found — 3
exploitdbwww.exploit-db.com/exploits/47000unverifiedgithubgithub.com/BBB-man/CVE-2019-3778-Spring-Security-OAuth-2.3-Open-Redirection★ 0cve_referencepacketstormsecurity.com/files/153299/Spring-Security-OAuth-2.3-Open-Redirection.htmlunverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.