Security Digest · Vulnerability record
CVE-2024-2083: Directory traversal in zenml
A directory traversal vulnerability exists in the zenml-io/zenml repository, specifically within the /api/v1/steps endpoint.
CVSS 9.9 Critical EPSS 37.5% · p99
Should you act?
High exploit likelihood
EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 37.5%, percentile 99: FIRST’s model estimates a 37.5% chance of exploitation activity in the next 30 days, higher than 99% of all scored CVEs (very high). EPSS is a probability, not a verdict.
- Needs an account (low (any account)). Exposure depends on who can log in.
- Only applies if your dependency tree includes
zenml(PyPI) < 0.55.5, fixed in 0.55.5. Check your lockfile, including transitive dependencies.
What it is
A directory traversal vulnerability exists in the zenml-io/zenml repository, specifically within the /api/v1/steps endpoint. Attackers can exploit this vulnerability by manipulating the 'logs' URI path in the request to fetch arbitrary file content, bypassing intended access restrictions. The vulnerability arises due to the lack of validation for directory traversal patterns, allowing attackers to access files outside of the restricted directory.
From the GitHub advisory
A directory traversal vulnerability exists in the zenml-io/zenml repository, specifically within the /api/v1/steps endpoint. Attackers can exploit this vulnerability by manipulating the 'logs' URI path in the request to fetch arbitrary file content, bypassing intended access restrictions. The vulnerability arises due to the lack of validation for directory traversal patterns, allowing attackers to access files outside of the restricted directory.
Weakness type: CWE-29.
Product: zenml (PyPI) · Assigned by: @huntr_ai · Published: 2024-04-16
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | zenml | < 0.55.5 | 0.55.5 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| zenml-io | zenml-io/zenml | unspecified < 0.55.5 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| @huntr_ai | 3.0 | 9.9 Critical | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.9 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: low (any account)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 37.49% probability of exploitation activity in the next 30 days; percentile 99.
Timeline
- — CVE record published by @huntr_ai
- — GitHub-reviewed advisory GHSA-6h3f-43vq-53hj published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-6h3f-43vq-53hj github.com
- CVE.org record CVE-2024-2083 cve.org
- NVD entry CVE-2024-2083 nvd.nist.gov
Other references from the CVE record and advisory
- huntr.com huntr.com
- github.com github.com
- github.com github.com