Skip to content

Privilege escalation in spring security

High severity GitHub Reviewed Published May 10, 2021 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

maven org.springframework.security:spring-security-bom (Maven)

Affected versions

>= 5.4.0, < 5.4.4
>= 5.3.0, < 5.3.8
< 5.2.9

Patched versions

5.4.4
5.3.8
5.2.9
maven org.springframework.security:spring-security-web (Maven)
< 5.2.9
>= 5.4.0, < 5.4.4
>= 5.3.0, < 5.3.8
5.2.9
5.4.4
5.3.8

Description

Spring Security 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, 5.2.x prior to 5.2.9.RELEASE, and older unsupported versions can fail to save the SecurityContext if it is changed more than once in a single request.A malicious user cannot cause the bug to happen (it must be programmed in). However, if the application's intent is to only allow the user to run with elevated privileges in a small portion of the application, the bug can be leveraged to extend those privileges to the rest of the application.

References

Published by the National Vulnerability Database Feb 23, 2021
Reviewed Mar 31, 2021
Published to the GitHub Advisory Database May 10, 2021
Last updated Feb 1, 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
Low
Privileges required
Low
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:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.259%
(66th percentile)

Weaknesses

CVE ID

CVE-2021-22112

GHSA ID

GHSA-gq28-h5vg-8prx

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.