# CVE-2019-10137: Path traversal in spacewalk-proxy

> Remote unauthenticated attackers can exploit a path traversal flaw in Spacewalk proxy to read arbitrary files or execute code via cached client tokens.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** Yes
- **Published:** 2 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-38jq-w3g8-jpc9, RHSA-2019:1663

## What is CVE-2019-10137?

CVE-2019-10137 is a high-severity path traversal vulnerability in Redhat Satellite, published on 2 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal flaw was found in spacewalk-proxy, all versions through 2.9, in the way the proxy processes cached client tokens. A remote, unauthenticated attacker could use this flaw to test the existence of arbitrary files, if they have access to the proxy's filesystem, or can execute arbitrary code in the context of the httpd process.

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

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `spacewalk-backend` | Red Hat:network_proxy:5.8::el6 | All versions | 0:2.5.3-177.el6sat |
| `spacewalk-backend-libs` | Red Hat:network_proxy:5.8::el6 | All versions | 0:2.5.3-177.el6sat |
| `spacewalk-proxy` | Red Hat:network_proxy:5.8::el6 | All versions | 0:2.5.0-8.el6sat |
| `spacewalk-proxy-broker` | Red Hat:network_proxy:5.8::el6 | All versions | 0:2.5.0-8.el6sat |
| `spacewalk-proxy-common` | Red Hat:network_proxy:5.8::el6 | All versions | 0:2.5.0-8.el6sat |
| `spacewalk-proxy-management` | Red Hat:network_proxy:5.8::el6 | All versions | 0:2.5.0-8.el6sat |
| `spacewalk-proxy-package-manager` | Red Hat:network_proxy:5.8::el6 | All versions | 0:2.5.0-8.el6sat |
| `spacewalk-proxy-redirect` | Red Hat:network_proxy:5.8::el6 | All versions | 0:2.5.0-8.el6sat |

Products: Redhat Satellite, Redhat Spacewalk.

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

Apply the vendor's patch.

## Is CVE-2019-10137 being exploited?

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

## Other vulnerabilities in Redhat Satellite

- [CVE-2024-7012](https://insights.sbomify.com/CVE-2024-7012/): Puppet-foreman: an authentication bypass vulnerability exists in foreman (critical 9.8)
- [CVE-2024-7923](https://insights.sbomify.com/CVE-2024-7923/): Puppet-pulpcore: an authentication bypass vulnerability exists in pulpcore (critical 9.8)
- [CVE-2026-96659](https://insights.sbomify.com/CVE-2026-96659/): Foreman: excessive permissions for viewer role on preview (critical 9.1)
- [CVE-2023-0118](https://insights.sbomify.com/CVE-2023-0118/): Foreman: arbitrary code execution through templates (critical 9.1)
- [CVE-2008-2369](https://insights.sbomify.com/CVE-2008-2369/): Hardcoded credentials in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10137 is a high-severity path traversal vulnerability in Redhat Satellite, published on 2 Jul 2019. 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-2019-10137 in the wild and no public exploit code.

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

## Sources

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

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