Elasticsearch-Hadoop: Deserialization of Untrusted Data
CVE-2023-46674 is a high-severity deserialization of untrusted data vulnerability in Elasticsearch-Hadoop from Elastic, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 7.17.11, 8.9.0 as the first without the flaw, so updating Elasticsearch-Hadoop to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.24% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Elasticsearch-Hadoop to 7.17.11 or 8.9.0, whichever matches your release line, or a later version.
- Update Elasticsearch to 7.17.11 or 8.9.0, whichever matches your release line, or a later version.
- Read the advisory on discuss.elastic.co for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Elastic | Elasticsearch-Hadoop | 1.3.0 up to, but not including, 7.17.11; 8.0.0 up to, but not including, 8.9.0 | 7.17.11, 8.9.0 |
| Elastic | Elasticsearch | before 7.17.11; 8.0.0 up to, but not including, 8.9.0 | 7.17.11, 8.9.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.0 | Medium | CNA (elastic.co) |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How developers prevent this class of flaw
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
- Explicitly define a final object() to prevent deserialization.
More Deserialization of Untrusted Data vulnerabilities (CWE-502)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Recent Deserialization of Untrusted Data vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.