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

Published 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

Affected Software

6 affected componentsFixes available
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
VMware Spring Security>=6.1.0<6.1.7
VMware Spring Security>=6.2.0<6.2.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.springframework.security:spring-security-core to a version that resolves this vulnerability.

    Fixed in 6.2.2
  2. Upgrade

    Upgrade maven/org.springframework.security:spring-security-core to a version that resolves this vulnerability.

    Fixed in 6.1.7
  3. Upgrade

    Upgrade redhat/spring-security to a version that resolves this vulnerability.

    Fixed in 6.1.7
  4. Upgrade

    Upgrade redhat/spring-security to a version that resolves this vulnerability.

    Fixed in 6.2.2
  5. Upgrade

    Upgrade Spring Security to a version that resolves this vulnerability.

    Fixed in 6.1.7
  6. Upgrade

    Upgrade Spring Security to a version that resolves this vulnerability.

    Fixed in 6.2.2

Event History

Feb 20, 2024
CVE Published
via MITRE·07:02 AM
Data Sourced
via MITRE·07:02 AM
DescriptionSeverity
Data Sourced
via NVD·07:15 AM
DescriptionSeverity
Data Sourced
via NVD·07:15 AM
WeaknessAffected Software
Advisory Published
via GitHub·09:30 AM
Data Sourced
via Red Hat·07:33 PM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-22234?

CVE-2024-22234 has a high severity rating due to its potential for broken access control.

2

How do I fix CVE-2024-22234?

To mitigate CVE-2024-22234, upgrade Spring Security to version 6.1.7 or 6.2.2.

3

What versions are affected by CVE-2024-22234?

CVE-2024-22234 affects Spring Security versions 6.1.x prior to 6.1.7 and 6.2.x prior to 6.2.2.

4

What does CVE-2024-22234 exploit in Spring Security?

CVE-2024-22234 exploits broken access control when using the AuthenticationTrustResolver.isFullyAuthenticated(Authentication) method.

5

Is there a workaround for CVE-2024-22234 until I can upgrade?

Currently, there are no documented workarounds for CVE-2024-22234, so updating to a remedial version is essential.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203