| Package | Affected versions | Patched versions |
|---|---|---|
| org.springframework.security:spring-security-bom | ≥ 5.3.0, < 5.3.8≥ 5.4.0, < 5.4.4< 5.2.9 | 5.3.85.4.45.2.9 |
| org.springframework.security:spring-security-web | ≥ 5.3.0, < 5.3.8≥ 5.4.0, < 5.4.4< 5.2.9 | 5.3.85.4.45.2.9 |
| communications element manager | ≥ 8.2.0, ≤ 8.2.4.0 | |
| communications interactive session recorder | = 6.3= 6.4 | |
| communications unified inventory management | = 7.4.1 | |
| hospitality cruise shipboard property management system | = 20.1.0 | |
| insurance policy administration | = 11.2.0= 11.3.0 | |
| mysql enterprise monitor | ≤ 8.0.25 | |
| spring security | ≥ 5.3.0, < 5.3.8< 5.2.9 | 5.3.85.2.9 |
| spring security | ≥ 5.4.0, < 5.4.4 | 5.4.4 |
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free