Privilege Escalation in spring-security-oauth2

Summary

Spring Security OAuth, versions 2.3 prior to 2.3.4, and 2.2 prior to 2.2.3, and 2.1 prior to 2.1.3, and 2.0 prior to 2.0.16, and older unsupported versions could be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can craft a request to the approval endpoint that can modify the previously saved authorization request and lead to a privilege escalation on the subsequent approval. This scenario can happen if the application is configured to use a custom approval endpoint that declares AuthorizationRequest as a controller method argument. This vulnerability exposes applications that meet all of the following requirements: Act in the role of an Authorization Server (e.g. @EnableAuthorizationServer) and use a custom Approval Endpoint that declares AuthorizationRequest as a controller method argument. This vulnerability does not expose applications that: Act in the role of an Authorization Server and use the default Approval Endpoint, act in the role of a Resource Server only (e.g. @EnableResourceServer), act in the role of a Client only (e.g. @EnableOAuthClient).

Timeline

1. Oct 18, 2018, 10:00 PM UTCCVE published
2. Sep 17, 2024, 1:16 AM UTCRecord last updated

Affected versions

• Pivotal Spring Security OAuth

  From 2.3 · through 2.3.3; From 2.2 · through 2.2.2; From 2.1 · through 2.1.2; From 2.0 · through 2.0.15

• org.springframework.security.oauth:spring-security-oauth2Maven

  From 2.0.0 · fixed in 2.0.16

• org.springframework.security.oauth:spring-security-oauth2Maven

  From 2.1.0 · fixed in 2.1.3

• org.springframework.security.oauth:spring-security-oauth2Maven

  From 2.2.0 · fixed in 2.2.3.RELEASE

• org.springframework.security.oauth:spring-security-oauth2Maven

  From 2.3.0 · fixed in 2.3.4.RELEASE

References 3