CVE-2024-38827: Spring Framework Authorization Bypass Due to Case Sensitivity Issues

Summary

02/12/2024
Yes i
Moderate
4.8

CVE-2024-38827: Spring Framework has Authorization Bypass for Case Sensitive Comparisons. Affects org.springframework.security:spring-security-core across 6 version ranges.

< 5.7.14 >= 5.8.0, < 5.8.16 >= 6.0.0, < 6.0.14 >= 6.1.0, < 6.1.12 >= 6.2.0, < 6.2.8 >= 6.3.0, < 6.3.5

Fixed in 6 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Also tracked for

The same CVE-2024-38827 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Spring Framework is a powerful framework for building Java applications, providing comprehensive infrastructure support for developing Java applications. It offers features such as dependency injection, aspect-oriented programming, and transaction management, making it a popular choice among developers. However, certain components of the Spring Framework, including spring-beans, spring-context, spring-core, spring-expression, and spring-jdbc, are vulnerable to an authorization bypass issue due to improper handling of case sensitivity in string comparisons.

Vulnerability Detail

The vulnerability arises from the use of String.toLowerCase() and String.toUpperCase() methods, which can exhibit locale-dependent behavior. This can lead to situations where authorization rules may not function as intended, allowing unauthorized access to resources. The potential ramifications include unauthorized users gaining access to sensitive data or functionalities that should be restricted, thereby compromising the security of applications built on the Spring Framework.

How To Fix

Latest published version: 7.2.0-RC1 as of 23 Oct 2026

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 5.7.14 5.7.14
  • >= 5.8.0, < 5.8.16 5.8.16
  • >= 6.0.0, < 6.0.14 6.0.14
  • >= 6.1.0, < 6.1.12 6.1.12
  • >= 6.2.0, < 6.2.8 6.2.8
  • >= 6.3.0, < 6.3.5 6.3.5

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, developers can implement custom authorization checks that are not reliant on case-sensitive string comparisons. This may involve using a more robust comparison method that accounts for locale variations or normalizing input strings before comparison.

Conclusion

In summary, CVE-2024-38827 presents a significant risk to applications using the Spring Framework due to an authorization bypass issue stemming from case sensitivity in string comparisons. It is crucial for developers to update to the patched version 6.1.14 or later to mitigate this vulnerability and ensure the security of their applications.

See every vulnerability recorded for org.springframework.security:spring-security-core →

Share this vulnerability

FAQ

CVE-2024-38827 is a vulnerability in the Spring Framework that allows for authorization bypass due to improper handling of case sensitivity in string comparisons.

The affected packages include spring-beans, spring-context, spring-core, spring-expression, and spring-jdbc.

The vulnerability can lead to unauthorized access to sensitive data or functionalities, compromising the security of applications built on the Spring Framework.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By simply checking your pom.xml, you can determine if your application is affected by this vulnerability.

The CVSS score for this vulnerability is 4.8, indicating a moderate severity level.

Related vulnerabilities

Recent vulnerabilities recorded for org.springframework.security:spring-security-core.

How To Fix

Latest published version: 7.2.0-RC1 as of 23 Oct 2026

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 5.7.14 5.7.14
  • >= 5.8.0, < 5.8.16 5.8.16
  • >= 6.0.0, < 6.0.14 6.0.14
  • >= 6.1.0, < 6.1.12 6.1.12
  • >= 6.2.0, < 6.2.8 6.2.8
  • >= 6.3.0, < 6.3.5 6.3.5

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback