CVE-2024-38807 json
CVE-2024-38807: Signature Forgery Vulnerability in Spring Boot's Loader
published 2024-08-23 2 y ago modified 2026-06-17 4 mo ago also GHSA-7cj3-x93g-gj76 , EUVD-2024-2526
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.springframework.boot:spring-boot-loader 2.7.22, 3.0.17, 3.1.13, 3.2.9, 3.3.3
- maven org.springframework.boot:spring-boot-loader-classic 2.7.22, 3.0.17, 3.1.13, 3.2.9, 3.3.3
- Spring Spring Boot 2.7.22, 3.0.17, 3.1.13, 3.2.9, 3.3.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 6.3 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.boot:spring-boot-loader | >=2.7.0, <2.7.22 >=3.0.0, <3.0.17 >=3.1.0, <3.1.13 >=3.2.0, <3.2.9 >=3.3.0, <3.3.3 |
2.7.22 3.0.17 3.1.13 3.2.9 3.3.3 |
| maven | org.springframework.boot:spring-boot-loader-classic | >=2.7.0, <2.7.22 >=3.0.0, <3.0.17 >=3.1.0, <3.1.13 >=3.2.0, <3.2.9 >=3.3.0, <3.3.3 |
2.7.22 3.0.17 3.1.13 3.2.9 3.3.3 |
Affected products
- Spring Spring Boot
Classification
- Weakness
- Technology feeds
References
Sources
- CVE List CVE-2024-38807
- GitHub Advisory GHSA-7cj3-x93g-gj76
- NVD CVE-2024-38807
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.