zenml-io/zenml: Path Traversal: '..filename'
CVE-2024-2083 is a critical-severity path traversal: '..filename' vulnerability in zenml-io/zenml from Zenml-io, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 0.55.5 as the first without the flaw, so updating zenml-io/zenml to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 37.2% chance of exploitation within 30 days, which is in the top 1.45% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update zenml-io/zenml to 0.55.5 or a later version.
- Update zenml to 0.55.5 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Zenml-io | zenml-io/zenml | before 0.55.5 | 0.55.5 |
| Zenmlio | zenml | before 0.55.5 | 0.55.5 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.9 | Critical | NVD |
| CVSS 3.0 | 9.9 | Critical | CNA (huntr.dev) |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Path Traversal: '..filename'
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '..filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.
How developers prevent this class of flaw
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/zenml-io/zenml/commit/00e934f33a243a554f5f65b80eefd5ea5117367bThird Party Advisory
Technical write-ups (may include proof of concept)
- huntr.com/bounties/f24b2216-6a4b-42a1-becb-9b47e6cf117fExploit, Issue Tracking, Third Party Advisory
Other vulnerabilities in zenml-io/zenml
- 7.8 High severity
- 7.5 High severity
- 8.8 High severity
Recent Path Traversal: '..filename' vulnerabilities
- 7.5 High severity
Spotted an error? Tell us.