Privilege escalation in spring security
Spring Security
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-bom Maven |
|
|
| org.springframework.security:spring-security-web |
Spring Security
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-bom Maven |
|
|
| org.springframework.security:spring-security-web |
|
|
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.
From the CVE record · vmware
Spring Security can fail to save the SecurityContext when an application changes it more than once in a single request. A malicious user cannot trigger this programming condition, but if it exists, they can leverage it to retain elevated privileges beyond the portion of the application where those privileges were intended.
Teams using the Maven spring-security-bom or spring-security-web packages should check 5.4.x before 5.4.4, 5.3.x before 5.3.8, 5.2.x before 5.2.9, and older unsupported versions.