# CVE-2018-17190: Remote Code Execution in spark-core

> Attackers can execute arbitrary code on the Apache Spark master host by sending a specially crafted request, bypassing the design that restricts execution to workers.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-phg2-9c5g-m4q7

## What is CVE-2018-17190?

CVE-2018-17190 is a critical code injection vulnerability in Apache Spark, published on 19 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In all versions of Apache Spark, its standalone resource manager accepts code to execute on a 'master' host, that then runs that code on 'worker' hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code too. Note that this does not affect standalone clusters with authentication enabled. While the master host typically has less outbound access to other resources than a worker, the execution of code on the master is nevertheless unexpected.

## Which versions are affected by CVE-2018-17190?

4 open source packages ship an affected version, including org.apache.spark:spark-core_2.10 and org.apache.spark:spark-core_2.11. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.spark:spark-core_2.10` | Maven | All versions | None |
| `org.apache.spark:spark-core_2.10` | Maven | All versions | None |
| `org.apache.spark:spark-core_2.11` | Maven | All versions | None |
| `org.apache.spark:spark-core_2.11` | Maven | All versions | None |

Products: Apache Spark.

## How do I fix CVE-2018-17190?

No fix has been published for CVE-2018-17190 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-17190 being exploited?

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

## Other vulnerabilities in Apache Spark

- [CVE-2022-33891](https://insights.sbomify.com/CVE-2022-33891/): Apache Spark Command Injection (high 8.8, exploited in the wild)
- [CVE-2020-9480](https://insights.sbomify.com/CVE-2020-9480/): Improper Authentication in Apache Spark (critical 9.8)
- [CVE-2019-20445](https://insights.sbomify.com/CVE-2019-20445/): HTTP Request Smuggling in Netty (critical 9.1)
- [CVE-2025-54920](https://insights.sbomify.com/CVE-2025-54920/): Apache Spark: Spark History Server Code Execution Vulnerability (high 8.8)
- [CVE-2023-32007](https://insights.sbomify.com/CVE-2023-32007/): Apache Spark: Shell command injection via Spark UI (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17190 and fix it if it is affected.

What it is: CVE-2018-17190 is a critical code injection vulnerability in Apache Spark, published on 19 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17190 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.spark:spark-core_2.10 (Maven): affected all versions; no fix listed
- org.apache.spark:spark-core_2.10 (Maven): affected all versions; no fix listed
- org.apache.spark:spark-core_2.11 (Maven): affected all versions; no fix listed
- org.apache.spark:spark-core_2.11 (Maven): affected all versions; no fix listed

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

## Sources

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

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