{"answers":{"affected":"3 open source packages ship an affected version, including org.elasticsearch:elasticsearch and elasticsearch. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-23451 in the wild and no public exploit code.","fix":"Upgrade org.elasticsearch:elasticsearch to 8.13.0 or later.","what":"CVE-2024-23451 is a medium-severity missing authorization vulnerability in Elastic Elasticsearch, published on 27 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-23451 and fix it if it is affected.\n\nWhat it is: CVE-2024-23451 is a medium-severity missing authorization vulnerability in Elastic Elasticsearch, published on 27 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-23451 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.elasticsearch:elasticsearch (Maven): affected from 8.10.0; fixed in 8.13.0\n- org.elasticsearch:elasticsearch (Maven): affected from 8.10.0; fixed in 8.13.0\n- elasticsearch (Bitnami): affected from 8.10.0; fixed in 8.13.0\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-23451/ (Markdown: https://insights.sbomify.com/CVE-2024-23451/index.md)","id":"CVE-2024-23451","markdown":"https://insights.sbomify.com/CVE-2024-23451/index.md","name":"CVE-2024-23451","record":{"aliases":["BIT-elasticsearch-2024-23451","GHSA-r3hx-qfh5-r9m7","UBUNTU-CVE-2024-23451"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Elasticsearch search engine","requires_auth":"high_privilege","summary":"A malicious user with a valid API key can read arbitrary documents from any index on a remote cluster using the custom transport protocol.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elasticsearch","vendor":"elastic"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Incorrect Authorization issue exists in the API key based security model for Remote Cluster Security, which is currently in Beta, in Elasticsearch 8.10.0 and before 8.13.0. This allows a malicious user with a valid API key for a remote cluster configured to use the new Remote Cluster Security to read arbitrary documents from any index on the remote cluster, and only if they use the Elasticsearch custom transport protocol to issue requests with the target index ID, the shard ID and the document ID. None of Elasticsearch REST API endpoints are affected by this issue.","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 Incorrect Authorization in the Remote Cluster Security API key based security model","id":"CVE-2024-23451","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"elastic:elasticsearch","products":["elastic:elasticsearch"],"type":"missing_authorization","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Apache bRPC: HTTP request smuggling vulnerability","id":"CVE-2024-23452"},"packages":[{"ecosystem":"Bitnami","fixed":["8.13.0"],"introduced":["8.10.0"],"last_affected":[],"package":"elasticsearch","purl":"pkg:bitnami/elasticsearch","source":"BIT-elasticsearch-2024-23451"},{"ecosystem":"Maven","fixed":["8.13.0"],"introduced":["8.10.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":null,"source":"GHSA-r3hx-qfh5-r9m7"},{"ecosystem":"Maven","fixed":["8.13.0"],"introduced":["8.10.0"],"last_affected":[],"package":"org.elasticsearch:elasticsearch","purl":"pkg:maven/org.elasticsearch/elasticsearch","source":"GHSA-r3hx-qfh5-r9m7"}],"prev":{"headline":"Elasticsearch Uncontrolled Resource Consumption vulnerability","id":"CVE-2024-23450"},"products":["Elasticsearch"],"published":"2024-03-27","related":[{"cvss_score":9.8,"headline":"Elasticsearch Groovy Scripting Engine Remote Code Execution","id":"CVE-2015-1427","kev_date_added":"2022-03-25","published":"2015-02-17"},{"cvss_score":8.1,"headline":"Elasticsearch Remote Code Execution","id":"CVE-2014-3120","kev_date_added":"2022-03-25","published":"2014-07-28"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2015-5377","kev_date_added":null,"published":"2018-03-06"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution","id":"CVE-2026-72649","kev_date_added":null,"published":"2026-09-01"},{"cvss_score":8.8,"headline":"Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process","id":"CVE-2026-72642","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":8.8,"headline":"Privilege Escalation Flaw in Elasticsearch","id":"CVE-2020-7014","kev_date_added":null,"published":"2020-06-03"},{"cvss_score":8.8,"headline":"Improper Privilege Management in Elasticsearch","id":"CVE-2020-7009","kev_date_added":null,"published":"2020-03-31"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Elastic"]},"summary":"A malicious user with a valid API key can read arbitrary documents from any index on a remote cluster using the custom transport protocol.","url":"https://insights.sbomify.com/CVE-2024-23451/"}