CVE-2023-46674GHSA-RV74-M283-5J95BIT-ELASTICSEARCH-2023-46674
Elasticsearch-hadoop Unsafe Deserialization
- 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
- Fix
- Fixed in 7.17.11, 8.9.0
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
An issue was identified that allowed the unsafe deserialization of java objects from hadoop or spark configuration properties that could have been modified by authenticated users. Elastic would like to thank Yakov Shafranovich, with Amazon Web Services for reporting this issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Elastic Elasticsearch-Hadoop
From 1.3.0 · fixed in 7.17.11; From 8.0.0 · fixed in 8.9.0
- org.elasticsearch:elasticsearch-hadoopMaven
fixed in 7.17.11
- org.elasticsearch:elasticsearch-hadoopMaven
From 8.0.0 · fixed in 8.9.0