Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2024-38807

MEDIUM

CVE-2024-38807 is a medium-severity (CVSS 6.3) CWE-290 vulnerability in org.springframework.boot:spring-boot-loader. O3 Security confirms whether CVE-2024-38807 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Signature forgery in Spring Boot's Loader

Also known asGHSA-7cj3-x93g-gj76
Published
Aug 23, 2024
Updated
Apr 10, 2026
Affected
10 pkgs
Patched
10 / 10
Exploits
None indexed

Blast Radius

10 pkgs affected
org.springframework.boot:spring-boot-loaderorg.springframework.boot:spring-boot-loader-classicorg.springframework.boot:spring-boot-loaderorg.springframework.boot:spring-boot-loader-classicorg.springframework.boot:spring-boot-loaderorg.springframework.boot:spring-boot-loader-classicorg.springframework.boot:spring-boot-loaderorg.springframework.boot:spring-boot-loader-classic+2 more

Real-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

10 total 10 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.springframework.boot:spring-boot-loader2.7.0&&< 2.7.222.7.22
Mavenorg.springframework.boot:spring-boot-loader-classic2.7.0&&< 2.7.222.7.22
Mavenorg.springframework.boot:spring-boot-loader3.0.0&&< 3.0.173.0.17
Mavenorg.springframework.boot:spring-boot-loader-classic3.0.0&&< 3.0.173.0.17
Mavenorg.springframework.boot:spring-boot-loader3.1.0&&< 3.1.133.1.13
Mavenorg.springframework.boot:spring-boot-loader-classic3.1.0&&< 3.1.133.1.13

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.boot:spring-boot-loader. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-38807 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-38807. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-38807 in your dependencies?

O3 detects CVE-2024-38807 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.