Authorization Bypass Through User-Controlled Key in Elastic Cloud Enterprise (ECE) Leading to Privilege Escalation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Elastic Cloud Enterprise (ECE), a platform for running and managing Elasticsearch deployments, is affected by this vulnerability. An attacker with access to any host in an ECE installation could obtain credentials meant for other platform roles, potentially gaining full control over the ECE control plane and the deployments it manages.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Authorization Bypass Through User-Controlled Key (CWE-639) in Elastic Cloud Enterprise (ECE) can lead to privilege escalation via Privilege Abuse (CAPEC-122). An attacker who controls any host in an ECE installation can obtain credentials that are reserved for other platform roles. These credentials can give the attacker full control of the ECE control plane and of the deployments that it manages.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Elastic Elastic Cloud Enterprise
From 1.0.0 · through 3.8.5; From 4.0.0 · through 4.2.0