Server stall via colliding QUIC connection identifiers
Published Feb 20, 2025 · Updated Feb 20, 2025
Hash-collision DoS in LiteSpeed Technologies LSQUIC before 4.2.0 allows remote attackers to stall servers via crafted QUIC SCIDs. The connection-management table indexes attacker-chosen Source Connection IDs with XXH32, so colliding identifiers degrade insertion and lookup operations toward quadratic work. Unauthenticated clients need only initiate many parallel QUIC connections; affected servers can spend most CPU time processing collision chains and stop serving traffic.
Summary
What happened
Hash-collision DoS in LiteSpeed Technologies LSQUIC before 4.2.0 allows remote attackers to stall servers via crafted QUIC SCIDs. The connection-management table indexes attacker-chosen Source Connection IDs with XXH32, so colliding identifiers degrade insertion and lookup operations toward quadratic work. Unauthenticated clients need only initiate many parallel QUIC connections; affected servers can spend most CPU time processing collision chains and stop serving traffic.
The record
- CVE
- CVE-2025-24947
- Published
- Feb 20, 2025
- Updated
- Feb 20, 2025
- Vendor
- LiteSpeed Technologies
- Product
- LSQUIC
- Classifications
- CWE-407, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2025CVE publishedPublication date reported by the CVE source.
- Feb 20, 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 <4.2.0
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