{"answers":{"affected":"5 open source packages ship an affected version, including org.elasticsearch:elasticsearch and elasticsearch. It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-31418 in the wild and no public exploit code.","fix":"Upgrade org.elasticsearch:elasticsearch to a fixed version for your release line: 7.17.13 or 8.9.0.","what":"CVE-2023-31418 is a high-severity denial of service vulnerability in Elastic Elasticsearch, published on 26 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-31418 and fix it if it is affected.\n\nWhat it is: CVE-2023-31418 is a high-severity denial of service vulnerability in Elastic Elasticsearch, published on 26 Oct 2023. 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-2023-31418 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.elasticsearch:elasticsearch (Maven): affected all versions; fixed in 7.17.13\n- org.elasticsearch:elasticsearch (Maven): affected all versions; fixed in 7.17.13\n- org.elasticsearch:elasticsearch (Maven): affected from 8.0.0; fixed in 8.9.0\n- org.elasticsearch:elasticsearch (Maven): affected from 8.0.0; fixed in 8.9.0\n- elasticsearch (Bitnami): affected all versions; fixed in 7.17.13, 8.8.3\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-2023-31418/ (Markdown: https://insights.sbomify.com/CVE-2023-31418/index.md)","id":"CVE-2023-31418","markdown":"https://insights.sbomify.com/CVE-2023-31418/index.md","name":"CVE-2023-31418","record":{"aliases":["BIT-elasticsearch-2023-31418","GHSA-2cqf-6xv9-f22w","MINI-q2jh-m7m4-mrhv","MINI-xppf-22vr-29w4","UBUNTU-CVE-2023-31418"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Elasticsearch search engine","requires_auth":"none","summary":"An unauthenticated attacker can cause Elasticsearch to crash via OutOfMemory errors by sending malformed HTTP requests, requiring an upgrade to mitigate.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elastic_cloud_enterprise","vendor":"elastic"},{"product":"elasticsearch","vendor":"elastic"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"An issue has been identified with how Elasticsearch handled incoming requests on the HTTP layer. An unauthenticated user could force an Elasticsearch node to exit with an OutOfMemory error by sending a moderate number of malformed HTTP requests. The issue was identified by Elastic Engineering and we have no indication that the issue is known or that it is being exploited in the wild.","ecosystems":["Bitnami","Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Elasticsearch uncontrolled resource consumption","id":"CVE-2023-31418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"elastic:elasticsearch","products":["elastic:elasticsearch"],"type":"denial_of_service","year":"2023"},"n_packages":5,"n_references":3,"next":{"headline":"Elasticsearch StackOverflow vulnerability","id":"CVE-2023-31419"},"packages":[{"ecosystem":"Bitnami","fixed":["7.17.13","8.8.3"],"introduced":["0","8.0.0"],"last_affected":[],"package":"elasticsearch","purl":"pkg:bitnami/elasticsearch","source":"BIT-elasticsearch-2023-31418"},{"ecosystem":"Maven","fixed":["7.17.13"],"introduced":["0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":null,"source":"GHSA-2cqf-6xv9-f22w"},{"ecosystem":"Maven","fixed":["7.17.13"],"introduced":["0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":"pkg:maven/org.elasticsearch/elasticsearch","source":"GHSA-2cqf-6xv9-f22w"},{"ecosystem":"Maven","fixed":["8.9.0"],"introduced":["8.0.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":null,"source":"GHSA-2cqf-6xv9-f22w"},{"ecosystem":"Maven","fixed":["8.9.0"],"introduced":["8.0.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":"pkg:maven/org.elasticsearch/elasticsearch","source":"GHSA-2cqf-6xv9-f22w"}],"prev":{"headline":"Elasticsearch Insertion of sensitive information in audit logs","id":"CVE-2023-31417"},"products":["Elasticsearch"],"published":"2023-10-26","related":[{"cvss_score":9.1,"headline":"Elastic Cloud Enterprise (ECE) Improper Neutralization of Special Elements Used in a Template Engine","id":"CVE-2025-37729","kev_date_added":null,"published":"2025-10-13"},{"cvss_score":8.8,"headline":"Elastic Cloud Enterprise Improper Authorization","id":"CVE-2025-37736","kev_date_added":null,"published":"2025-11-07"},{"cvss_score":8.1,"headline":"Privilege escalation in Elastic Cloud Enterprise","id":"CVE-2024-37282","kev_date_added":null,"published":"2024-06-28"},{"cvss_score":7.5,"headline":"Information disclosure in Elastic Cloud Enterprise","id":"CVE-2018-3828","kev_date_added":null,"published":"2018-09-19"},{"cvss_score":6.5,"headline":"Information disclosure in Elastic Cloud Enterprise","id":"CVE-2022-23715","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":5.9,"headline":"Hardcoded credentials in Elastic Cloud Enterprise (ECE)","id":"CVE-2018-3825","kev_date_added":null,"published":"2018-09-19"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-02-13","vendors":["Elastic"]},"summary":"An unauthenticated attacker can cause Elasticsearch to crash via OutOfMemory errors by sending malformed HTTP requests, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2023-31418/"}