Bug 2271929 (CVE-2024-23451)

Summary: CVE-2024-23451 elasticsearch: Incorrect authorization issue in Remote Cluster Security
Product: [Other] Security Response Reporter: Marco Benatto <mbenatto>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: bdettelb, caswilli, dkuc, eglynn, fjansen, jcantril, jjoyce, jschluet, kaycoth, lhh, lsvaty, mburns, mgarciac, mmagr, periklis, pgrist
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: elasticsearch-8.13.0 Doc Type: If docs needed, set a value
Doc Text:
An incorrect authorization flaw was found in the API key based security model for Remote Cluster Security in the elasticsearch package. A malicious user with a valid API key can leverage this issue to gain access to read any documents from any index in the remote cluster, exposing possible sensitive information and having a high impact on data confidentiality. Exploitation of this flaw is only possible if the elasticsearch cluster custom transport protocol is configured to issue requests with the target index ID, the shared ID, and the document ID. This issue doesn't affect elasticsearch REST API endpoints.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2271930, 2271931    
Bug Blocks: 2271932    

Description Marco Benatto 2024-03-27 19:12:43 UTC
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.

https://discuss.elastic.co/t/elasticsearch-8-13-0-security-update-esa-2024-07/356315