# CVE-2024-38827: Spring Security Authorization Bypass for Case Sensitive Comparisons > Attackers can bypass authorization rules due to locale-dependent string comparison flaws in Spring Security, potentially gaining unauthorized access. - **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Dec 2024 - **Updated:** 24 Jan 2025 - **Also known as:** CLEANSTART-2026-QB96901, ECHO-74b0-b853-7934, GHSA-q3v6-hm2v-pw99, ROOT-APP-MAVEN-CVE-2024-38827 ## What is CVE-2024-38827? CVE-2024-38827 is a medium-severity authentication bypass vulnerability in Spring Security, published on 2 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The usage of String.toLowerCase() and String.toUpperCase() has some Locale dependent exceptions that could potentially result in authorization rules not working properly. Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key) ## Which versions are affected by CVE-2024-38827? 12 open source packages ship an affected version, including org.springframework.security:spring-security-core. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.security:spring-security-core` | Maven | All versions | 5.7.14 | | `org.springframework.security:spring-security-core` | Maven | All versions | 5.7.14 | | `org.springframework.security:spring-security-core` | Maven | From 5.8.0 | 5.8.16 | | `org.springframework.security:spring-security-core` | Maven | From 5.8.0 | 5.8.16 | | `org.springframework.security:spring-security-core` | Maven | From 6.0.0 | 6.0.14 | | `org.springframework.security:spring-security-core` | Maven | From 6.0.0 | 6.0.14 | | `org.springframework.security:spring-security-core` | Maven | From 6.1.0 | 6.1.12 | | `org.springframework.security:spring-security-core` | Maven | From 6.1.0 | 6.1.12 | | `org.springframework.security:spring-security-core` | Maven | From 6.2.0 | 6.2.8 | | `org.springframework.security:spring-security-core` | Maven | From 6.2.0 | 6.2.8 | | `org.springframework.security:spring-security-core` | Maven | From 6.3.0 | 6.3.5 | | `org.springframework.security:spring-security-core` | Maven | From 6.3.0 | 6.3.5 | ## How do I fix CVE-2024-38827? Upgrade org.springframework.security:spring-security-core to a fixed version for your release line: 5.7.14, 5.8.16, 6.0.14 or 6.1.12. ## Is CVE-2024-38827 being exploited? There is no known exploitation of CVE-2024-38827 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-38827 and fix it if it is affected. What it is: CVE-2024-38827 is a medium-severity authentication bypass vulnerability in Spring Security, published on 2 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-38827 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.security:spring-security-core (Maven): affected all versions; fixed in 5.7.14 - org.springframework.security:spring-security-core (Maven): affected all versions; fixed in 5.7.14 - org.springframework.security:spring-security-core (Maven): affected from 5.8.0; fixed in 5.8.16 - org.springframework.security:spring-security-core (Maven): affected from 5.8.0; fixed in 5.8.16 - org.springframework.security:spring-security-core (Maven): affected from 6.0.0; fixed in 6.0.14 - org.springframework.security:spring-security-core (Maven): affected from 6.0.0; fixed in 6.0.14 - org.springframework.security:spring-security-core (Maven): affected from 6.1.0; fixed in 6.1.12 - org.springframework.security:spring-security-core (Maven): affected from 6.1.0; fixed in 6.1.12 - org.springframework.security:spring-security-core (Maven): affected from 6.2.0; fixed in 6.2.8 - org.springframework.security:spring-security-core (Maven): affected from 6.2.0; fixed in 6.2.8 - org.springframework.security:spring-security-core (Maven): affected from 6.3.0; fixed in 6.3.5 - org.springframework.security:spring-security-core (Maven): affected from 6.3.0; fixed in 6.3.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-38827/ (Markdown: https://insights.sbomify.com/CVE-2024-38827/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38827 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38827 - OSV: https://osv.dev/vulnerability/CVE-2024-38827 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-38827/ Summaries are generated and may contain mistakes; the official description above is the record.