Authorization Flaw in org.elasticsearch:elasticsearch (CVE-2024-23451)
Summary
Vulnerability in org.elasticsearch:elasticsearch (CVE-2024-23451). Confidential information can be exposed externally. Mitigation: upgrade to 8.13.0 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2024-23451 has been found in org.elasticsearch:elasticsearch.
Confidential information can be exposed externally.
What to do: upgrade org.elasticsearch:elasticsearch to 8.13.0 or later.
If unsure, ask your IT team or search "org.elasticsearch:elasticsearch CVE-2024-23451" on the vendor's site.
CVE-2024-23451 (org.elasticsearch:elasticsearch) — CWE-863
Attack vector: remote (network-reachable) / no user interaction
Patched: 8.13.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in org.elasticsearch:elasticsearch.
Check the vendor advisory for the affected versions of org.elasticsearch:elasticsearch.
Severity: ?. Confidential information can be exposed externally.
Update to 8.13.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.elasticsearch:elasticsearch を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.elasticsearch:elasticsearch to 8.13.0ステージング環境で 8.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web discuss.elastic.co