cve.bz

CVE-2024-38807 spring spring boot: Authentication Bypass by Spoofing

6.3 mediumEPSS 0.1%Fix available

Medium (6.3) in spring spring boot. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.boot:spring-boot-loader 2.7.22, 3.0.17, 3.1.13.

On this page
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.

Severity

CVSS 3.1

6.3 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-08-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-290 Authentication Bypass by Spoofing
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • org.springframework.boot:spring-boot-loader (Maven): fixed in 2.7.22, 3.0.17, 3.1.13, 3.2.9, 3.3.3
  • org.springframework.boot:spring-boot-loader-classic (Maven): fixed in 2.7.22, 3.0.17, 3.1.13, 3.2.9, 3.3.3

Ask an AI about this CVE

Show the promptExplain CVE-2024-38807 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-38807?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-38807?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-38807 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Bootfrom 2.7.x before 2.7.22
Spring Bootfrom 3.0.x before 3.0.17
Spring Bootfrom 3.1.x before 3.1.13
Spring Bootfrom 3.2.x before 3.2.9
Spring Bootfrom 3.3.x before 3.3.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader>=2.7.0 <2.7.222.7.22
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader-classic>=2.7.0 <2.7.222.7.22
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader>=3.0.0 <3.0.173.0.17
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader-classic>=3.0.0 <3.0.173.0.17
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader>=3.1.0 <3.1.133.1.13
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader-classic>=3.1.0 <3.1.133.1.13
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader>=3.2.0 <3.2.93.2.9
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader-classic>=3.2.0 <3.2.93.2.9
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader>=3.3.0 <3.3.33.3.3
GHSA-7cj3-x93g-gj76Mavenorg.springframework.boot:spring-boot-loader-classic>=3.3.0 <3.3.33.3.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libspring-javano fix listedDEBIAN-CVE-2024-38807
Ubuntu25.10, 26.04:LTS, 26.10 and 6 morelibspring-javano fix listedUBUNTU-CVE-2024-38807

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-461 Web Services API Signature Forgery Leveraging Hash Function Extension Weakness Severity: High
  • CAPEC-473 Signature Spoof

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-290.

References

Check your stackJSON