cve.bz

CVE-2024-39702 openresty openresty: Inefficient Algorithmic Complexity

5.9 mediumEPSS 0.6%Fix available

Medium (5.9) in openresty openresty. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
In lj_str_hash.c in OpenResty 1.19.3.1 through 1.25.3.1, the string hashing function (used during string interning) allows HashDoS (Hash Denial of Service) attacks. An attacker could cause excessive resource usage during proxy operations via crafted requests, potentially leading to a denial of service with relatively few incoming requests. This vulnerability only exists in the OpenResty fork in the openresty/luajit2 GitHub repository. The LuaJIT/LuaJIT repository. is unaffected.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-07-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-407 Inefficient Algorithmic Complexity
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-39702 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-39702?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-39702?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-39702 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openresty:openrestyfrom 1.19.3.1 before 1.19.9.2
openresty:openrestyfrom 1.21.4.1 before 1.21.4.4
openresty:openresty1.25.3.1

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The HashDoS vulnerability in OpenResty’s `lj_str_hash.c` file, while impactful, is classified as a moderate severity issue rather than critical. This classification is due to the nature of the attack vector, which requires crafted input to exploit the hashing function and induce excessive resource usage. The exploitability of this vulnerability depends on the attacker’s ability to generate and send specifically designed requests, which may limit its practical impact compared to vulnerabilities that allow for more straightforward or widespread attacks. Additionally, the effect is confined to resource exhaustion, which, although disruptive, does not directly lead to unauthorized data access or system compromise.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat 3scale API Management Platform 2openrestyWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-39702.

References

Check your stackJSON