Skip to content

Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated

High severity GitHub Reviewed Published Feb 20, 2024 to the GitHub Advisory Database • Updated Mar 15, 2024

Package

maven org.springframework.security:spring-security-core (Maven)

Affected versions

>= 6.1.0, < 6.1.7
>= 6.2.0, < 6.2.2

Patched versions

6.1.7
6.2.2

Description

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:

References

Published by the National Vulnerability Database Feb 20, 2024
Published to the GitHub Advisory Database Feb 20, 2024
Reviewed Feb 21, 2024
Last updated Mar 15, 2024

Severity

High
7.4
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Weaknesses

CVE ID

CVE-2024-22234

GHSA ID

GHSA-w3w6-26f2-p474

Credits

Checking history
See something to contribute? Suggest improvements for this vulnerability.