CVE-2018-15758

Privilege Escalation in spring-security-oauth2

CRITICAL
9.6
CVSS Score
Published: October 18, 2018 at 10:00 PM UTC
Updated: June 17, 2026 at 01:43 AM UTC
1 product affected across 1 vendorSpring Security OAuth

Using Spring Security OAuth by Pivotal?

Get instant alerts when new vulnerabilities affect Spring Security OAuth - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL9.6
Exploit prediction
EPSS 2%

Description

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 1.0.52.0 ≤ v ≤ 2.0.152.0.0 ≤ v < 2.0.162.1 ≤ v ≤ 2.1.22.1.0 ≤ v < 2.1.32.2 ≤ v ≤ 2.2.22.2.0 ≤ v < 2.2.32.3 ≤ v ≤ 2.3.32.3.0 ≤ v < 2.3.42.02.12.22.3
Affected range stops below 2.0.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.2.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

VDB Entryx_refsource_BIDThird Party Advisory
http://www.securityfocus.com/bid/105687
x_refsource_CONFIRMMitigationVendor Advisory
https://pivotal.io/security/cve-2018-15758

CVSS

9.6CRITICALdell
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card