# CVE-2024-38820: CVE-2024-38820: Spring Framework DataBinder Case Sensitive Match Exception > Locale-dependent case sensitivity issues in Spring DataBinder allow attackers to bypass field protection mechanisms, potentially exposing sensitive data. - **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 18 Oct 2024 - **Updated:** 29 Nov 2024 - **Also known as:** CLEANSTART-2026-IC44335, CLSA-2025-1744156857, CLSA-2026-1781657689, CLSA-2026-1784682932, CLSA-2026-1790795899, DEBIAN-CVE-2024-38820, ECHO-a425-eab7-94ca, GHSA-4gc7-5j7h-4qph, MINI-cpm2-97fx-8qf6, MINI-cwm2-857p-45fg, ROOT-APP-MAVEN-CVE-2024-38820, UBUNTU-CVE-2024-38820 ## What is CVE-2024-38820? CVE-2024-38820 is a low-severity vulnerability in Vmware Spring Framework, published on 18 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description The fix for CVE-2022-22968 made disallowedFields patterns in DataBinder case insensitive. However, String.toLowerCase() has some Locale dependent exceptions that could potentially result in fields not protected as expected. Weakness: CWE-178 (Improper Handling of Case Sensitivity) ## Which versions are affected by CVE-2024-38820? 12 open source packages ship an affected version, including org.springframework:spring-context and org.springframework:spring-web. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework:spring-context` | Maven | All versions to 5.3.40 | None | | `org.springframework:spring-context` | Maven | All versions to 5.3.40 | None | | `org.springframework:spring-context` | Maven | From 6.0.0 to 6.0.24 | None | | `org.springframework:spring-context` | Maven | From 6.0.0 to 6.0.24 | None | | `org.springframework:spring-context` | Maven | From 6.1.0 | 6.1.14 | | `org.springframework:spring-context` | Maven | From 6.1.0 | 6.1.14 | | `org.springframework:spring-web` | Maven | All versions to 5.3.40 | None | | `org.springframework:spring-web` | Maven | All versions to 5.3.40 | None | | `org.springframework:spring-web` | Maven | From 6.0.0 to 6.0.24 | None | | `org.springframework:spring-web` | Maven | From 6.0.0 to 6.0.24 | None | | `org.springframework:spring-web` | Maven | From 6.1.0 | 6.1.14 | | `org.springframework:spring-web` | Maven | From 6.1.0 | 6.1.14 | Products: Vmware Spring Framework. ## How do I fix CVE-2024-38820? Upgrade org.springframework:spring-context to 6.1.14 or later. ## Is CVE-2024-38820 being exploited? There is no known exploitation of CVE-2024-38820 in the wild and no public exploit code. Public exploit code: - https://github.com/kadamnayan/POC-CVE-2024-38820 (github_poc): https://github.com/kadamnayan/POC-CVE-2024-38820 ## Other vulnerabilities in Vmware Spring Framework - [CVE-2026-47884](https://insights.sbomify.com/CVE-2026-47884/): Spring Framework Improper Path Limitation in XsltView (critical 9.8) - [CVE-2026-47890](https://insights.sbomify.com/CVE-2026-47890/): Spring Framework Server Sent Event stream corruption while rendering fragments (critical 9.8) - [CVE-2026-47891](https://insights.sbomify.com/CVE-2026-47891/): Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder (critical 9.8) - [CVE-2026-47892](https://insights.sbomify.com/CVE-2026-47892/): Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints (critical 9.8) - [CVE-2026-59313](https://insights.sbomify.com/CVE-2026-59313/): Server Sent Event stream corruption in Spring MVC functional web framework (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-38820 and fix it if it is affected. What it is: CVE-2024-38820 is a low-severity vulnerability in Vmware Spring Framework, published on 18 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-38820 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework:spring-context (Maven): affected all versions up to 5.3.40; no fix listed - org.springframework:spring-context (Maven): affected all versions up to 5.3.40; no fix listed - org.springframework:spring-context (Maven): affected from 6.0.0 up to 6.0.24; no fix listed - org.springframework:spring-context (Maven): affected from 6.0.0 up to 6.0.24; no fix listed - org.springframework:spring-context (Maven): affected from 6.1.0; fixed in 6.1.14 - org.springframework:spring-context (Maven): affected from 6.1.0; fixed in 6.1.14 - org.springframework:spring-web (Maven): affected all versions up to 5.3.40; no fix listed - org.springframework:spring-web (Maven): affected all versions up to 5.3.40; no fix listed - org.springframework:spring-web (Maven): affected from 6.0.0 up to 6.0.24; no fix listed - org.springframework:spring-web (Maven): affected from 6.0.0 up to 6.0.24; no fix listed - org.springframework:spring-web (Maven): affected from 6.1.0; fixed in 6.1.14 - org.springframework:spring-web (Maven): affected from 6.1.0; fixed in 6.1.14 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-38820/ (Markdown: https://insights.sbomify.com/CVE-2024-38820/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38820 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38820 - OSV: https://osv.dev/vulnerability/CVE-2024-38820 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-38820/ Summaries are generated and may contain mistakes; the official description above is the record.