# CVE-2024-38807: CVE-2024-38807: Signature Forgery Vulnerability in Spring Boot's Loader > Attackers can forge signatures in nested JARs, bypassing verification in Spring Boot applications using custom signature checks. - **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Aug 2024 - **Updated:** 27 Mar 2025 - **Also known as:** CLSA-2025-1738627240, CLSA-2026-1778460303, CLSA-2026-1780620670, CLSA-2026-1785291684, CLSA-2026-1790861577, DEBIAN-CVE-2024-38807, ECHO-bba1-f0f4-8c29, GHSA-7cj3-x93g-gj76, RHLW-2026-11ab22698dd7c623, ROOT-APP-MAVEN-CVE-2024-38807, UBUNTU-CVE-2024-38807 ## What is CVE-2024-38807? CVE-2024-38807 is a medium-severity vulnerability in Spring Boot, published on 23 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Applications that use spring-boot-loader or spring-boot-loader-classic and contain custom code that performs signature verification of nested jar files may be vulnerable to signature forgery where content that appears to have been signed by one signer has, in fact, been signed by another. Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-290 (Authentication Bypass by Spoofing) ## Which versions are affected by CVE-2024-38807? 20 open source packages ship an affected version, including org.springframework.boot:spring-boot-loader and org.springframework.boot:spring-boot-loader-classic. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.boot:spring-boot-loader` | Maven | From 2.7.0 | 2.7.22 | | `org.springframework.boot:spring-boot-loader` | Maven | From 2.7.0 | 2.7.22 | | `org.springframework.boot:spring-boot-loader` | Maven | From 3.0.0 | 3.0.17 | | `org.springframework.boot:spring-boot-loader` | Maven | From 3.0.0 | 3.0.17 | | `org.springframework.boot:spring-boot-loader` | Maven | From 3.1.0 | 3.1.13 | | `org.springframework.boot:spring-boot-loader` | Maven | From 3.1.0 | 3.1.13 | | `org.springframework.boot:spring-boot-loader` | Maven | From 3.2.0 | 3.2.9 | | `org.springframework.boot:spring-boot-loader` | Maven | From 3.2.0 | 3.2.9 | | `org.springframework.boot:spring-boot-loader` | Maven | From 3.3.0 | 3.3.3 | | `org.springframework.boot:spring-boot-loader` | Maven | From 3.3.0 | 3.3.3 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 2.7.0 | 2.7.22 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 2.7.0 | 2.7.22 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 3.0.0 | 3.0.17 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 3.0.0 | 3.0.17 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 3.1.0 | 3.1.13 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 3.1.0 | 3.1.13 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 3.2.0 | 3.2.9 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 3.2.0 | 3.2.9 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 3.3.0 | 3.3.3 | | `org.springframework.boot:spring-boot-loader-classic` | Maven | From 3.3.0 | 3.3.3 | ## How do I fix CVE-2024-38807? Upgrade org.springframework.boot:spring-boot-loader to a fixed version for your release line: 2.7.22, 3.0.17, 3.1.13 or 3.2.9. ## Is CVE-2024-38807 being exploited? There is no known exploitation of CVE-2024-38807 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-38807 and fix it if it is affected. What it is: CVE-2024-38807 is a medium-severity vulnerability in Spring Boot, published on 23 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-38807 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.boot:spring-boot-loader (Maven): affected from 2.7.0; fixed in 2.7.22 - org.springframework.boot:spring-boot-loader (Maven): affected from 2.7.0; fixed in 2.7.22 - org.springframework.boot:spring-boot-loader (Maven): affected from 3.0.0; fixed in 3.0.17 - org.springframework.boot:spring-boot-loader (Maven): affected from 3.0.0; fixed in 3.0.17 - org.springframework.boot:spring-boot-loader (Maven): affected from 3.1.0; fixed in 3.1.13 - org.springframework.boot:spring-boot-loader (Maven): affected from 3.1.0; fixed in 3.1.13 - org.springframework.boot:spring-boot-loader (Maven): affected from 3.2.0; fixed in 3.2.9 - org.springframework.boot:spring-boot-loader (Maven): affected from 3.2.0; fixed in 3.2.9 - org.springframework.boot:spring-boot-loader (Maven): affected from 3.3.0; fixed in 3.3.3 - org.springframework.boot:spring-boot-loader (Maven): affected from 3.3.0; fixed in 3.3.3 - org.springframework.boot:spring-boot-loader-classic (Maven): affected from 2.7.0; fixed in 2.7.22 - org.springframework.boot:spring-boot-loader-classic (Maven): affected from 2.7.0; fixed in 2.7.22 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-38807/ (Markdown: https://insights.sbomify.com/CVE-2024-38807/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38807 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38807 - OSV: https://osv.dev/vulnerability/CVE-2024-38807 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-38807/ Summaries are generated and may contain mistakes; the official description above is the record.