CPU exhaustion via unbounded primality testing
Published Mar 1, 2024 · Updated Apr 22, 2025
Denial of service in phpseclib 1.x before 1.0.23, 2.x before 2.0.47, and 3.x before 3.0.36 allows attackers to exhaust CPU with a malformed certificate. Certificate parsing passes an attacker-sized prime to BigInteger::isPrime(), which performs primality testing without a bit-length limit. Exposure requires an application to process attacker-controlled certificates; exploitation ties up CPU without reported data disclosure or modification.
Summary
What happened
Denial of service in phpseclib 1.x before 1.0.23, 2.x before 2.0.47, and 3.x before 3.0.36 allows attackers to exhaust CPU with a malformed certificate. Certificate parsing passes an attacker-sized prime to BigInteger::isPrime(), which performs primality testing without a bit-length limit. Exposure requires an application to process attacker-controlled certificates; exploitation ties up CPU without reported data disclosure or modification.
The record
- CVE
- CVE-2024-27354
- Published
- Mar 1, 2024
- Updated
- Apr 22, 2025
- Vendor
- phpseclib
- Product
- phpseclib
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 2024CVE publishedPublication date reported by the CVE source.
- Apr 22, 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.0.23
- Affected versionversion=0 <2.0.47
- Affected versionversion=0 <3.0.36
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