First published: Tue Feb 20 2024(Updated: )
In Spring Security, versions 6.1.x prior to 6.1.7 and versions 6.2.x prior to 6.2.2, an application is vulnerable to broken access control when it directly uses the AuthenticationTrustResolver.isFullyAuthenticated(Authentication) method. Specifically, an application is vulnerable if: * The application uses AuthenticationTrustResolver.isFullyAuthenticated(Authentication) directly and a null authentication parameter is passed to it resulting in an erroneous true return value. An application is not vulnerable if any of the following is true: * The application does not use AuthenticationTrustResolver.isFullyAuthenticated(Authentication) directly. * The application does not pass null to AuthenticationTrustResolver.isFullyAuthenticated * The application only uses isFullyAuthenticated via Method Security https://docs.spring.io/spring-security/reference/servlet/authorization/method-security.html or HTTP Request Security https://docs.spring.io/spring-security/reference/servlet/authorization/authorize-http-requests.html
Credit: security@vmware.com security@vmware.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.springframework.security:spring-security-core | >=6.2.0<6.2.2 | 6.2.2 |
maven/org.springframework.security:spring-security-core | >=6.1.0<6.1.7 | 6.1.7 |
redhat/spring-security | <6.1.7 | 6.1.7 |
redhat/spring-security | <6.2.2 | 6.2.2 |
Spring Security | >=6.1.0<6.1.7 | |
Spring Security | >=6.2.0<6.2.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-22234 has a high severity rating due to its potential for broken access control.
To mitigate CVE-2024-22234, upgrade Spring Security to version 6.1.7 or 6.2.2.
CVE-2024-22234 affects Spring Security versions 6.1.x prior to 6.1.7 and 6.2.x prior to 6.2.2.
CVE-2024-22234 exploits broken access control when using the AuthenticationTrustResolver.isFullyAuthenticated(Authentication) method.
Currently, there are no documented workarounds for CVE-2024-22234, so updating to a remedial version is essential.