Signature forgery via inconsistent nested JAR parsing
Published Aug 23, 2024 · Updated Mar 27, 2025
Signature forgery in affected Spring Boot releases allows local users to make a nested JAR appear signed by a different signer. NestedJarFile reads archive content with its standard-mode ZipContent parser but verifies signatures with streaming JarInputStream, so crafted ZIP ambiguities give the two parsers different contents. Exploitation requires local low-privileged access, a crafted nested JAR, and application-specific signature-verification code; accepted content can be read or modified under the wrong signer's trust.
Summary
What happened
Signature forgery in affected Spring Boot releases allows local users to make a nested JAR appear signed by a different signer. NestedJarFile reads archive content with its standard-mode ZipContent parser but verifies signatures with streaming JarInputStream, so crafted ZIP ambiguities give the two parsers different contents. Exploitation requires local low-privileged access, a crafted nested JAR, and application-specific signature-verification code; accepted content can be read or modified under the wrong signer's trust.
The record
- CVE
- CVE-2024-38807
- Published
- Aug 23, 2024
- Updated
- Mar 27, 2025
- Vendor
- Spring
- Product
- Spring Boot
- Classifications
- CWE-290, CWE-347, T1553.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 23, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.7.x <2.7.22
- Affected versionversion=3.0.x <3.0.17
- Affected versionversion=3.1.x <3.1.13
- Affected versionversion=3.2.x <3.2.9
- Affected versionversion=3.3.x <3.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo