cve.bz

CVE-2019-10137 redhat: Path traversal

9.8 criticalEPSS 3.1%

Critical (9.8) in redhat. EPSS 3.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.0

9.8 critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
3.1% (unchanged from 3.1% a week ago; 3.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 88th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-10137 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-10137?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-10137?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-10137 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
redhat:satellite5.0
redhat:spacewalkthrough 2.9

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatnetwork_proxy:5.8::el6spacewalk-backend, spacewalk-backend-libs0:2.5.3-177.el6satRHSA-2019:1663
Red Hatnetwork_proxy:5.8::el6spacewalk-proxy, spacewalk-proxy-broker, spacewalk-proxy-common and 3 more0:2.5.0-8.el6satRHSA-2019:1663
SUSEManager Proxy 3.2release-notes-susemanager-proxy3.2.9-0.16.27.1SUSE-SU-2019:1790-1
SUSEManager Proxy 3.2spacewalk-proxy2.8.5.6-3.11.1SUSE-SU-2019:1790-1
SUSEManager Proxy 3.2, Manager Server 3.2spacewalk-backend2.8.57.17-3.33.1SUSE-SU-2019:1790-1
SUSEManager Proxy 3.2, Manager Server 3.2spacewalk-web2.8.7.17-3.30.1SUSE-SU-2019:1790-1
SUSEManager Proxy Module 4.0spacewalk-proxy4.0.12-3.3.1SUSE-SU-2019:1789-1
SUSEManager Proxy Module 4.0, Manager Server Module 4.0spacewalk-backend4.0.22-3.3.1SUSE-SU-2019:1789-1
SUSEManager Proxy Module 4.0, Manager Server Module 4.0spacewalk-web4.0.14-3.3.1SUSE-SU-2019:1789-1
SUSEManager Server 3.2release-notes-susemanager3.2.9-6.35.1SUSE-SU-2019:1790-1
SUSEManager Server Module 4.0susemanager-docs_en, susemanager-doc-indexes4.0-10.3.1SUSE-SU-2019:1789-1
SUSEManager Server Module 4.0susemanager-sync-data4.0.12-3.3.1SUSE-SU-2019:1789-1

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat · SUSE.

Red Hat

Red Hat rates this Important.

Red Hat's mitigation

SELinux in enforcing mode will prevent the proxy to access files that have an incompatible SELinux context

ProductPackageStateAdvisory
Red Hat Satellite Proxy v 5.8spacewalk-backend-0:2.5.3-177.el6satFixed 2019-07-02RHSA-2019:1663
Red Hat Satellite Proxy v 5.8spacewalk-proxy-0:2.5.0-8.el6satFixed 2019-07-02RHSA-2019:1663

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-10137.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON