# CVE-2018-11804: Improper Input Validation in Apache Spark

> A vulnerability in Spark's build script allows external attackers to read files accessible to the developer account running the build.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-62g2-m955-v383

## What is CVE-2018-11804?

CVE-2018-11804 is a high-severity vulnerability in Apache Spark, published on 24 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Spark's Apache Maven-based build includes a convenience script, 'build/mvn', that downloads and runs a zinc server to speed up compilation. It has been included in release branches since 1.3.x, up to and including master. This server will accept connections from external hosts by default. A specially-crafted request to the zinc server could cause it to reveal information in files readable to the developer account running the build. Note that this issue does not affect end users of Spark, only developers building Spark from source code.

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

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 | From 1.3.0 to 2.1.3 | None |
| `org.apache.spark:spark-core_2.10` | Maven | From 1.3.0 to 2.1.3 | None |
| `org.apache.spark:spark-core_2.11` | Maven | From 1.3.0 to 2.1.3 | None |
| `org.apache.spark:spark-core_2.11` | Maven | From 1.3.0 to 2.1.3 | None |

Products: Apache Spark.

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

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

## Is CVE-2018-11804 being exploited?

There is no known exploitation of CVE-2018-11804 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-2018-17190](https://insights.sbomify.com/CVE-2018-17190/): Remote Code Execution in spark-core (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11804 is a high-severity vulnerability in Apache Spark, published on 24 Oct 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-11804 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.spark:spark-core_2.10 (Maven): affected from 1.3.0 up to 2.1.3; no fix listed
- org.apache.spark:spark-core_2.10 (Maven): affected from 1.3.0 up to 2.1.3; no fix listed
- org.apache.spark:spark-core_2.11 (Maven): affected from 1.3.0 up to 2.1.3; no fix listed
- org.apache.spark:spark-core_2.11 (Maven): affected from 1.3.0 up to 2.1.3; 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-11804/ (Markdown: https://insights.sbomify.com/CVE-2018-11804/index.md)
```

## Sources

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

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