CVE-2024-38807 — spring-boot-loader
MEDIUMCVE-2024-38807 is a medium-severity (CVSS 6.3) CWE-290 vulnerability in org.springframework.boot:spring-boot-loader. A fix is available for org.springframework.boot:spring-boot-loader — see the affected versions and patch details below.
Signature forgery in Spring Boot's Loader
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-38807.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.boot:spring-boot-loader☕org.springframework.boot:spring-boot-loader-classic☕org.springframework.boot:spring-boot-loader☕org.springframework.boot:spring-boot-loader-classic☕org.springframework.boot:spring-boot-loader☕org.springframework.boot:spring-boot-loader-classic☕org.springframework.boot:spring-boot-loader☕org.springframework.boot:spring-boot-loader-classic+2 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.boot:spring-boot-loader | ≥ 2.7.0&&< 2.7.22 | 2.7.22org.springframework.boot:spring-boot-loader:2.7.22 |
| ☕Maven | org.springframework.boot:spring-boot-loader-classic | ≥ 2.7.0&&< 2.7.22 | 2.7.22org.springframework.boot:spring-boot-loader-classic:2.7.22 |
| ☕Maven | org.springframework.boot:spring-boot-loader | ≥ 3.0.0&&< 3.0.17 | 3.0.17org.springframework.boot:spring-boot-loader:3.0.17 |
| ☕Maven | org.springframework.boot:spring-boot-loader-classic | ≥ 3.0.0&&< 3.0.17 | 3.0.17org.springframework.boot:spring-boot-loader-classic:3.0.17 |
| ☕Maven | org.springframework.boot:spring-boot-loader | ≥ 3.1.0&&< 3.1.13 | 3.1.13org.springframework.boot:spring-boot-loader:3.1.13 |
| ☕Maven | org.springframework.boot:spring-boot-loader-classic | ≥ 3.1.0&&< 3.1.13 | 3.1.13org.springframework.boot:spring-boot-loader-classic:3.1.13 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-loader, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.boot:spring-boot-loader to 2.7.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-38807 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2024-38807 in your dependencies?
Find it across Maven, including transitive dependencies.