mlflow/mlflow: Path Traversal: '..filename'
CVE-2024-8859 is a high-severity path traversal: '..filename' vulnerability in mlflow/mlflow from Mlflow, with a CVSS 3.0 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2.17.0 as the first without the flaw, so updating mlflow/mlflow to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.77% chance of exploitation within 30 days, higher than 87% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update mlflow/mlflow to 2.17.0 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Mlflow | mlflow/mlflow | before 2.17.0 | 2.17.0 |
| Lfprojects | Mlflow | 2.15.1 | Not stated |
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
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by CNA (huntr.dev).
Official description
A path traversal vulnerability exists in mlflow/mlflow version 2.15.1. When users configure and use the dbfs service, concatenating the URL directly into the file protocol results in an arbitrary file read vulnerability. This issue occurs because only the path part of the URL is checked, while parts such as query and parameters are not handled. The vulnerability is triggered if the user has configured the dbfs service, and during usage, the service is mounted to a local 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: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Technical write-ups (may include proof of concept)
- huntr.com/bounties/2259b88b-a0c6-4c7c-b434-6aacf6056dcbExploit, Third Party Advisory
Other vulnerabilities in mlflow/mlflow
- 8.1 High severity
- 7.7 High severity
- 9.0 Critical severity
- 9.6 Critical severity
- 7.8 High severity
- 8.6 High severity
Recent Path Traversal: '..filename' vulnerabilities
- 9.1 Critical severity
- 7.2 High severity
- 9.1 Critical severity
- 8.8 High severity
- 8.8 High severity
- 8.2 High severity
Spotted an error? Tell us.