# CVE-2023-46674: Elasticsearch-hadoop Unsafe Deserialization

> Authenticated users can achieve remote code execution via unsafe deserialization of Java objects in Elasticsearch-Hadoop configuration properties.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2023
- **Updated:** 28 Aug 2024
- **Also known as:** BIT-elasticsearch-2023-46674, GHSA-rv74-m283-5j95

## What is CVE-2023-46674?

CVE-2023-46674 is a medium-severity unsafe deserialization vulnerability in Elastic Elasticsearch, published on 5 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2023-46674?

5 open source packages ship an affected version, including org.elasticsearch:elasticsearch-hadoop and elasticsearch. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.elasticsearch:elasticsearch-hadoop` | Maven | All versions | 7.17.11 |
| `org.elasticsearch:elasticsearch-hadoop` | Maven | All versions | 7.17.11 |
| `org.elasticsearch:elasticsearch-hadoop` | Maven | From 8.0.0 | 8.9.0 |
| `org.elasticsearch:elasticsearch-hadoop` | Maven | From 8.0.0 | 8.9.0 |
| `elasticsearch` | Bitnami | All versions | 7.17.11, 8.9.0 |

Products: Elastic Elasticsearch.

## How do I fix CVE-2023-46674?

Upgrade org.elasticsearch:elasticsearch-hadoop to a fixed version for your release line: 7.17.11 or 8.9.0.

## Is CVE-2023-46674 being exploited?

There is no known exploitation of CVE-2023-46674 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Elasticsearch

- [CVE-2015-1427](https://insights.sbomify.com/CVE-2015-1427/): Elasticsearch Groovy Scripting Engine Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2014-3120](https://insights.sbomify.com/CVE-2014-3120/): Elasticsearch Remote Code Execution (high 8.1, exploited in the wild)
- [CVE-2015-5377](https://insights.sbomify.com/CVE-2015-5377/): Code injection in n/a (critical 9.8)
- [CVE-2026-72649](https://insights.sbomify.com/CVE-2026-72649/): Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution (high 8.8)
- [CVE-2026-72642](https://insights.sbomify.com/CVE-2026-72642/): Use of Out-of-range Pointer Offset in the Elasticsearch Machine Learning Native Inference Process (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46674 and fix it if it is affected.

What it is: CVE-2023-46674 is a medium-severity unsafe deserialization vulnerability in Elastic Elasticsearch, published on 5 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46674 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.elasticsearch:elasticsearch-hadoop (Maven): affected all versions; fixed in 7.17.11
- org.elasticsearch:elasticsearch-hadoop (Maven): affected all versions; fixed in 7.17.11
- org.elasticsearch:elasticsearch-hadoop (Maven): affected from 8.0.0; fixed in 8.9.0
- org.elasticsearch:elasticsearch-hadoop (Maven): affected from 8.0.0; fixed in 8.9.0
- elasticsearch (Bitnami): affected all versions; fixed in 7.17.11, 8.9.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-46674/ (Markdown: https://insights.sbomify.com/CVE-2023-46674/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46674
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46674
- OSV: https://osv.dev/vulnerability/CVE-2023-46674

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-46674/
Summaries are generated and may contain mistakes; the official description above is the record.