# CVE-2018-9159: Moderate severity vulnerability that affects com.sparkjava:spark-core

> Remote attackers can read unintended static files via path traversal in the Spark Java library, exposing sensitive data.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** Yes
- **Published:** 31 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-76qr-mmh8-cp8f, SUSE-SU-2018:2689-1

## What is CVE-2018-9159?

CVE-2018-9159 is a medium-severity path traversal vulnerability in n/a, published on 31 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Spark before 2.7.2, a remote attacker can read unintended static files via various representations of absolute or relative pathnames, as demonstrated by file: URLs and directory traversal sequences. NOTE: this product is unrelated to Ignite Realtime Spark.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including com.sparkjava:spark-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.sparkjava:spark-core` | Maven | All versions | 2.7.2 |
| `com.sparkjava:spark-core` | Maven | All versions | 2.7.2 |
| `spark` | SUSE:Manager Server 3.1 | All versions | 2.3-3.3.1 |

Products: Sparkjava Spark.

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

Upgrade com.sparkjava:spark-core to 2.7.2 or later.

## Is CVE-2018-9159 being exploited?

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

Public exploit code:

- https://github.com/shoucheng3/perwendel__spark_CVE-2018-9159_2-7-1 (github_poc): https://github.com/shoucheng3/perwendel__spark_CVE-2018-9159_2-7-1
- https://github.com/shoucheng3/perwendel__spark_CVE-2018-9159_2_7_2_fixed (github_poc): https://github.com/shoucheng3/perwendel__spark_CVE-2018-9159_2_7_2_fixed

## Other vulnerabilities in n/a

- [CVE-2016-9177](https://insights.sbomify.com/CVE-2016-9177/): Spark allows remote attackers to read arbitrary files via a .. (dot dot) in the URI (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-9159 is a medium-severity path traversal vulnerability in n/a, published on 31 Mar 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-9159 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.sparkjava:spark-core (Maven): affected all versions; fixed in 2.7.2
- com.sparkjava:spark-core (Maven): affected all versions; fixed in 2.7.2

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

## Sources

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

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