Proxy denial of service via hash collisions
Published Jul 23, 2024 · Updated Nov 26, 2024
Hash denial of service in OpenResty 1.19.3.1 through 1.25.3.1 allows remote attackers to exhaust resources via crafted proxy requests. The lj_str_hash.c string-interning path uses an optimized CRC32-based hash for short strings, enabling attacker-chosen collisions to drive excessive hash-table work. A relatively small request volume can severely degrade proxy performance, but the flaw is limited to the OpenResty LuaJIT branch on SSE 4.2 builds.
Summary
What happened
Hash denial of service in OpenResty 1.19.3.1 through 1.25.3.1 allows remote attackers to exhaust resources via crafted proxy requests. The lj_str_hash.c string-interning path uses an optimized CRC32-based hash for short strings, enabling attacker-chosen collisions to drive excessive hash-table work. A relatively small request volume can severely degrade proxy performance, but the flaw is limited to the OpenResty LuaJIT branch on SSE 4.2 builds.
The record
- CVE
- CVE-2024-39702
- Published
- Jul 23, 2024
- Updated
- Nov 26, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-407, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2024CVE publishedPublication date reported by the CVE source.
- Nov 26, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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