Sign in
Deutsch English Español Polski
High

Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated

  • Disclosed: 20.02.2024
  • Updated: 11.10.2026 12:21

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:

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) org.springframework.security:spring-security-core >= 6.1.0, < 6.1.7, >= 6.2.0, < 6.2.2 6.1.7, 6.2.2

References

CVSS score 7.4/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-284
Platform
Java / Kotlin (Maven)
Package
org.springframework.security:spring-security-core
Disclosed
20.02.2024
Updated
11.10.2026 12:21

Sources and licenses

OSV / GitHub Advisory Database - GHSA-w3w6-26f2-p474 - CC BY 4.0

Vulnerability history: org.springframework.security:spring-security-core

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (31) in the archive
Total entries
31
First → latest
10.2018 04.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 4
  • High 11
  • Medium 15
  • Low 1

Disclosures per year

Severity:
  1. Spring Security annotation detection mechanism has authorization bypass
    High · 7.5 CVE-2025-41248 >= 6.4.0, < 6.4.10, >= 6.5.0, < 6.5.4 6.4.10, 6.5.4
  2. Spring Security authorization bypass for method security annotations on private methods
    Critical · 9.1 CVE-2025-41232 >= 6.4.0, < 6.4.6 6.4.6
  3. Erroneous authentication pass in Spring Security
    High · 8.2 CVE-2024-22257 < 5.7.12, >= 5.8.0, < 5.8.11, >= 6.0.0, < 6.1.8, >= 6.2.0, < 6.2.3 5.7.12, 5.8.11, 6.1.8, 6.2.3
  4. Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated this entry
    High · 7.4 CVE-2024-22234 >= 6.1.0, < 6.1.7, >= 6.2.0, < 6.2.2 6.1.7, 6.2.2
  5. Spring Security authorization rules can be bypassed via forward or include dispatcher types
    Critical · 9.8 CVE-2022-31692 >= 5.7.0, < 5.7.5, >= 5.6.0, < 5.6.9 5.7.5, 5.6.9
  6. Authorization bypass in Spring Security
    Critical · 9.8 CVE-2022-22978 >= 5.5.0, < 5.5.7, >= 5.6.0, < 5.6.4, < 5.4.11 5.5.7, 5.6.4, 5.4.11
  7. Deserialization of Untrusted Data in Spring Security
    High · 8.1 CVE-2017-4995 >= 4.2.0.RELEASE, < 4.2.3.RELEASE, >= 5.0.0.M1, < 5.0.0.M2 4.2.3.RELEASE, 5.0.0.M2
  8. Improper Authentication in Spring Security
    High · 7.3 CVE-2014-0097 >= 3.2.0, < 3.2.2.RELEASE, >= 3.1.0, < 3.1.5.RELEASE 3.2.2.RELEASE, 3.1.5.RELEASE
  9. Resource Exhaustion in Spring Security
    High · 7.5 CVE-2021-22119 >= 5.5.0, < 5.5.1, >= 5.4.0, < 5.4.7, >= 5.3.0, < 5.3.10, >= 5.2.0, < 5.2.11 5.5.1, 5.4.7, 5.3.10, 5.2.11
  10. Security Constraint Bypass in Spring Security
    High · 7.5 CVE-2016-9879 < 3.2.10.RELEASE, >= 4.0.0.RELEASE, < 4.1.4.RELEASE, >= 4.2.0.RELEASE, < 4.2.1.RELEASE 3.2.10.RELEASE, 4.1.4.RELEASE, 4.2.1.RELEASE
  11. Authorization Bypass in Spring Security
    Critical · 9.8 CVE-2014-3527 < 3.1.7, >= 3.2.0, < 3.2.5 3.1.7, 3.2.5
  12. Signature wrapping vulnerability in Spring Security
    High · 8.8 CVE-2020-5407 >= 5.2.0, < 5.2.4, >= 5.3.0, < 5.3.2 5.2.4, 5.3.2
  13. Insufficiently Protected Credentials and Improper Authentication in Spring Security
    High · 7.3 CVE-2019-11272 < 4.2.13 4.2.13
  14. Spring Security vulnerable to Authorization Bypass
    High · 7.4 CVE-2018-15801 >= 5.1.0, < 5.1.2 5.1.2
  15. Spring Security and Spring Framework may not recognize certain paths that should be protected
    High · 7.5 CVE-2016-5007 < 4.1.1 4.1.1

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Privacy policy

Free to subscribe. Unsubscribe with one click in any email.