Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated

HIGH | FEBRUARY 19, 2024 | CVE-2024-22234

Description

In Spring Security, 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 or HTTP Request Security

Affected Spring Products and Versions

Spring Security:

  • 6.2.0 - 6.2.1
  • 6.1.0 - 6.1.6

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
6.2.2OSS
6.1.7OSS

No further mitigation steps are necessary.

Credit

This issue was identified and responsibly reported by Rogério Sorroche (https://github.com/rogeriosorroche).

History

  • 2024-02-19: Initial vulnerability report published.

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

Tanzu Spring offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all