CVE-2024-22234: Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated

Summary

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

Timeline

1. Feb 20, 2024, 7:02 AM UTCCVE published
2. Feb 21, 2024, 7:46 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Feb 13, 2025, 5:33 PM UTCRecord last updated

Affected versions

• Spring Spring Security

  From 6.1.x · fixed in 6.1.7; From 6.2.x · fixed in 6.2.2

• org.springframework.security:spring-security-coreMaven

  From 6.1.0 · fixed in 6.1.7

• org.springframework.security:spring-security-coreMaven

  From 6.2.0 · fixed in 6.2.2

References 2