CVE-2024-38807
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApplications 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApplications using spring-boot-loader or spring-boot-loader-classic with custom code that performs signature verification of nested JAR files are vulnerable to signature forgery. The vulnerability allows content that appears to be signed by one entity to actually have been signed by a different entity, enabling attackers to bypass signature-based trust decisions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify spring-boot-loader dependency usageReview your project's pom.xml, build.gradle, or dependency management to find if spring-boot-loader or spring-boot-loader-classic is listed as a direct or transitive dependencyAffected if Either spring-boot-loader or spring-boot-loader-classic is present in the project dependencies
-
Check the spring-boot-loader versionLocate the specific version number of spring-boot-loader or spring-boot-loader-classic in your build configuration or the nested JAR file META-INF/MANIFEST.MF entry for Implementation-VersionAffected if The version is older than the fixed release (the vulnerability affects versions prior to the patched release)
-
Determine if custom signature verification existsSearch your codebase for custom code that performs signature verification on nested JAR files, look for classes that implement JarEntry/jar verification, or code referencing JarInputStream, JarVerifier, or similar signature validation APIsAffected if Custom code that verifies signatures of nested JAR entries is present
-
Inspect nested JAR handling configurationExamine how your application handles nested JARs (WAR/JAR packaging), look for code that extracts or processes entries from nested JARs (files within BOOT-INF/lib/ or APP-INF/lib/)Affected if The application processes or loads classes/resources from nested JARs in a way that could bypass signature verification logic
-
Verify signature validation logic scopeReview your signature verification code to confirm whether it validates the actual signer identity (including distinguishing between different signing entities) versus just checking that a signature existsAffected if The verification logic does not properly validate the actual signer identity across nested JAR boundaries
You are affected if your application uses spring-boot-loader or spring-boot-loader-classic with custom signature verification code for nested JAR files, and the library version is older than the patched release.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReview and update custom signature verification logic for nested JAR files to properly validate the actual signer identity and ensure verification is not circumvented by the nested JAR handling mechanism.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-38807 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-38807 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data