# CVE-2023-46673: Elasticsearch Improper Handling of Exceptional Conditions

> Malformed scripts in the Ingest Pipeline can crash Elasticsearch nodes via the Simulate Pipeline API, causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** BIT-elasticsearch-2023-46673, GHSA-285m-vhfq-xx4h, MINI-f3hf-jr9w-6v5q, MINI-fp42-mgj2-g3mh, UBUNTU-CVE-2023-46673

## What is CVE-2023-46673?

CVE-2023-46673 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 22 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

It was identified that malformed scripts used in the script processor of an Ingest Pipeline could cause an Elasticsearch node to crash when calling the Simulate Pipeline API.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.elasticsearch:elasticsearch` | Maven | From 7.0.0 | 7.17.14 |
| `org.elasticsearch:elasticsearch` | Maven | From 7.0.0 | 7.17.14 |
| `org.elasticsearch:elasticsearch` | Maven | From 8.0.0 | 8.10.3 |
| `org.elasticsearch:elasticsearch` | Maven | From 8.0.0 | 8.10.3 |
| `elasticsearch` | Bitnami | From 7.0.0 | 7.17.14, 8.10.3 |

Products: Elastic Elasticsearch.

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

Upgrade org.elasticsearch:elasticsearch to a fixed version for your release line: 7.17.14 or 8.10.3.

## Is CVE-2023-46673 being exploited?

There is no known exploitation of CVE-2023-46673 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-46673 and fix it if it is affected.

What it is: CVE-2023-46673 is a medium-severity denial of service vulnerability in Elastic Elasticsearch, published on 22 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46673 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.elasticsearch:elasticsearch (Maven): affected from 7.0.0; fixed in 7.17.14
- org.elasticsearch:elasticsearch (Maven): affected from 7.0.0; fixed in 7.17.14
- org.elasticsearch:elasticsearch (Maven): affected from 8.0.0; fixed in 8.10.3
- org.elasticsearch:elasticsearch (Maven): affected from 8.0.0; fixed in 8.10.3
- elasticsearch (Bitnami): affected from 7.0.0; fixed in 7.17.14, 8.10.3

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-46673/ (Markdown: https://insights.sbomify.com/CVE-2023-46673/index.md)
```

## Sources

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

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