Service interruption via mishandled chunked encoding
Published May 22, 2024 · Updated Feb 13, 2025
Resource exhaustion in OpenLiteSpeed before 1.8.1 allows remote attackers to interrupt service via chunked HTTP requests. LiteSpeed has not published which chunk-decoding locus mishandles input or whether memory, CPU, or connection state is consumed without a limit. The HTTP listener is reachable without authentication, and the reported consequence is limited to degraded availability rather than data access or modification.
Summary
What happened
Resource exhaustion in OpenLiteSpeed before 1.8.1 allows remote attackers to interrupt service via chunked HTTP requests. LiteSpeed has not published which chunk-decoding locus mishandles input or whether memory, CPU, or connection state is consumed without a limit. The HTTP listener is reachable without authentication, and the reported consequence is limited to degraded availability rather than data access or modification.
The record
- CVE
- CVE-2024-31617
- Published
- May 22, 2024
- Updated
- Feb 13, 2025
- Vendor
- LiteSpeed Technologies
- Product
- OpenLiteSpeed
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 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.8.1
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