Skip to content

spring-security-oauth2-client vulnerable to Privilege Escalation

High severity GitHub Reviewed Published Nov 1, 2022 to the GitHub Advisory Database • Updated Jan 31, 2023

Package

maven org.springframework.security:spring-security-oauth2-client (Maven)

Affected versions

>= 5.7.0, < 5.7.5
< 5.6.9

Patched versions

5.7.5
5.6.9

Description

Spring Security, versions 5.7 prior to 5.7.5, and 5.6 prior to 5.6.9, and older unsupported versions could be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can modify a request initiated by the Client (via the browser) to the Authorization Server which can lead to a privilege escalation on the subsequent approval. This scenario can happen if the Authorization Server responds with an OAuth2 Access Token Response containing an empty scope list (per RFC 6749, Section 5.1) on the subsequent request to the token endpoint to obtain the access token.

References

Published by the National Vulnerability Database Oct 31, 2022
Published to the GitHub Advisory Database Nov 1, 2022
Reviewed Nov 1, 2022
Last updated Jan 31, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.250%
(66th percentile)

Weaknesses

CVE ID

CVE-2022-31690

GHSA ID

GHSA-32vj-v39g-jh23

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.