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

• Spring Security
  • 6.1.0 to 6.1.6
  • 6.2.0 to 6.2.1

Users of affected versions should apply the following mitigation. 6.1.x users should upgrade to 6.1.7. 6.2.x users should upgrade to 6.2.2. No other steps are necessary.  Releases that have fixed this issue include:

• Spring Security
  • 6.1.7
  • 6.2.2

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