# CVE-2019-17050: Path traversal in n/a

> Admins with Compass access can read or delete arbitrary files, including sensitive configuration files, by exploiting path traversal vulnerabilities.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9v7c-rj74-pc33

## What is CVE-2019-17050?

CVE-2019-17050 is a high-severity path traversal vulnerability in n/a, published on 30 Sep 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in the Voyager package through 1.2.7 for Laravel. An attacker with admin privileges and Compass access can read or delete arbitrary files, such as the .env file. NOTE: a software maintainer has suggested a solution in which Compass is switched off in a production environment.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2019-17050?

It affects 1 product.


Products: Thecontrolgroup Voyager.

## How do I fix CVE-2019-17050?

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

## Is CVE-2019-17050 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36070](https://insights.sbomify.com/CVE-2020-36070/): Remote code execution in Voyager (critical 9.8)
- [CVE-2024-55415](https://insights.sbomify.com/CVE-2024-55415/): DevDojo Voyager vulnerable to path traversal (medium 5.7)
- [CVE-2024-55417](https://insights.sbomify.com/CVE-2024-55417/): DevDojo Voyager Arbitrary File Write (medium 4.3)
- [CVE-2024-55416](https://insights.sbomify.com/CVE-2024-55416/): DevDojo Voyager vulnerable to reflected Cross-site Scripting (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17050 and fix it if it is affected.

What it is: CVE-2019-17050 is a high-severity path traversal vulnerability in n/a, published on 30 Sep 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17050 in the wild and no public exploit code.

Affected product: n/a. 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-2019-17050/ (Markdown: https://insights.sbomify.com/CVE-2019-17050/index.md)
```

## Sources

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

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