CPU exhaustion via unbounded F2m field size
Published May 9, 2024 · Updated Feb 13, 2025
Resource consumption in affected Bouncy Castle Java, Java FIPS, and C# .NET releases allows attackers to interrupt applications. The ECCurve F2m constructor accepts an attacker-controlled m field size without a maximum bound, causing excessive work when a crafted X.509 public key is extracted. Exposure is limited to applications that accept explicit F2m parameter sets or invoke the constructor from imported code; named-curve-only paths, including TLS, are not affected.
Summary
What happened
Resource consumption in affected Bouncy Castle Java, Java FIPS, and C# .NET releases allows attackers to interrupt applications. The ECCurve F2m constructor accepts an attacker-controlled m field size without a maximum bound, causing excessive work when a crafted X.509 public key is extracted. Exposure is limited to applications that accept explicit F2m parameter sets or invoke the constructor from imported code; named-curve-only paths, including TLS, are not affected.
The record
- CVE
- CVE-2024-29857
- Published
- May 9, 2024
- Updated
- Feb 13, 2025
- Vendor
- Legion of the Bouncy Castle Inc.
- Product
- Bouncy Castle Java
- Classifications
- CWE-400, CWE-125, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 9, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=0 <=1.77
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