{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-39702 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-39702 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-39702 is a medium-severity denial of service vulnerability in n/a, published on 23 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-39702 and fix it if it is affected.\n\nWhat it is: CVE-2024-39702 is a medium-severity denial of service vulnerability in n/a, published on 23 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-39702 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-39702/ (Markdown: https://insights.sbomify.com/CVE-2024-39702/index.md)","id":"CVE-2024-39702","markdown":"https://insights.sbomify.com/CVE-2024-39702/index.md","name":"CVE-2024-39702","record":{"aliases":["GHSA-6px8-752j-c2vv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenResty web server","requires_auth":"none","summary":"An attacker can cause denial of service in OpenResty by sending crafted requests that trigger excessive resource usage in the string hashing function.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"openresty","vendor":"openresty"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2024-39702","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in ThreatQ","id":"CVE-2024-39703"},"packages":[],"prev":{"headline":"Directus Incorrectly handles _in` filter","id":"CVE-2024-39701"},"products":["n/a"],"published":"2024-07-23","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2018-9230","kev_date_added":null,"published":"2018-04-02"},{"cvss_score":7.5,"headline":"OpenResty: Buffer overflow when writing PROXY protocol v2 header to upstream","id":"CVE-2026-55233","kev_date_added":null,"published":"2026-07-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-26","vendors":["n/a"]},"summary":"An attacker can cause denial of service in OpenResty by sending crafted requests that trigger excessive resource usage in the string hashing function.","url":"https://insights.sbomify.com/CVE-2024-39702/"}