# CVE-2017-14804: package builds could use directory traversal to write outside of target area

> Attackers can exploit directory traversal in the build package to write files outside the intended buildroot, potentially leading to code execution or privilege escalation.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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:** 1 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-14804, GHSA-q7c2-6g86-6v93, SUSE-SU-2019:0387-1, UBUNTU-CVE-2017-14804, openSUSE-SU-2019:0232-1

## What is CVE-2017-14804?

CVE-2017-14804 is a critical path traversal vulnerability in Opensuse Leap, published on 1 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The build package before 20171128 did not check directory names during extraction of build results that allowed untrusted builds to write outside of the target system,allowing escape out of buildroots.

Weakness: CWE-20 (Improper Input Validation), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2017-14804?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `build` | SUSE:Linux Enterprise Module for Development Tools 15 | All versions | 20190128-3.3.2 |
| `build` | openSUSE:Leap 15.0 | All versions | 20190128-lp150.2.3.1 |

Products: Opensuse Leap, Suse Linux Enterprise Software Development Kit.

## How do I fix CVE-2017-14804?

Upgrade to a fixed version.

## Is CVE-2017-14804 being exploited?

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

## Other vulnerabilities in Opensuse Leap

- [CVE-2015-4902](https://insights.sbomify.com/CVE-2015-4902/): Oracle Java SE Integrity Check (medium 5.3, exploited in the wild)
- [CVE-2019-20787](https://insights.sbomify.com/CVE-2019-20787/): Teeworlds before 0.7.4 has an integer overflow when computing a tilemap size. (critical 9.8)
- [CVE-2019-8341](https://insights.sbomify.com/CVE-2019-8341/): Code injection in n/a (critical 9.8)
- [CVE-2019-6438](https://insights.sbomify.com/CVE-2019-6438/): Other in n/a (critical 9.8)
- [CVE-2017-18215](https://insights.sbomify.com/CVE-2017-18215/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14804 and fix it if it is affected.

What it is: CVE-2017-14804 is a critical path traversal vulnerability in Opensuse Leap, published on 1 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14804 in the wild and no public exploit code.

Affected product: Opensuse Leap. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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