CVE-2023-2780
published 2023-05-17CVE-2023-2780: Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1.
PriorityP263critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EXPLOIT
EPSS
6.31%
92.7th percentile
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| lfprojects | mlflow | < 2.3.1 | 2.3.1 |
| lfprojects | mlflow | >= 0 < 2.3.0 | 2.3.0 |
| lfprojects | mlflow | >= 0 < fae77a525dd908c56d6204a4cef1c1c75b4e9857 | fae77a525dd908c56d6204a4cef1c1c75b4e9857 |
| lfprojects | mlflow | >= 0 < 2.3.1 | 2.3.1 |
| mlflow | mlflow_mlflow | >= unspecified < 2.3.1 | 2.3.1 |
Detection & IOCsextracted from sources · hover to see the quote
- →Successful exploitation is confirmed by matching 'root:.*:0:0:' in the HTTP 200 response body, indicating /etc/passwd was returned. ↗
- →Shodan/FOFA fingerprinting: exposed MLflow instances can be identified via HTTP title 'mlflow'. Use shodan-query 'http.title:"mlflow"' or FOFA 'title="mlflow"' to find targets. ↗
- ·The exploit requires no authentication (PR:N, UI:N per CVSS), but the three-step chain must be executed in sequence: model creation → version creation with malicious source → artifact fetch. The 'version' value must be extracted dynamically from the model-versions/create response before the final GET request. ↗
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv3.09.8CRITICALCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ghsa9.8CRITICAL
osv9.8CRITICAL
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
mlflow Path Traversal vulnerability
ghsa·2023-05-17·CVSS 9.8
CVE-2023-2780 [CRITICAL] CWE-29 mlflow Path Traversal vulnerability
mlflow Path Traversal vulnerability
mlflow prior to 2.3.0 is vulnerable to path traversal due to a bypass of the fix for CVE-2023-1177.
OSV
CVE-2023-2780: Path Traversal: '\
osv·2023-05-17
CVE-2023-2780 CVE-2023-2780: Path Traversal: '\
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1.
OSV
mlflow Path Traversal vulnerability
osv·2023-05-17·CVSS 9.8
CVE-2023-2780 [CRITICAL] mlflow Path Traversal vulnerability
mlflow Path Traversal vulnerability
mlflow prior to 2.3.0 is vulnerable to path traversal due to a bypass of the fix for CVE-2023-1177.
No detection rules found.
Nuclei
Mlflow <2.3.1 - Local File Inclusion Bypass
nuclei·CVSS 9.8
CVE-2023-2780 [CRITICAL] Mlflow <2.3.1 - Local File Inclusion Bypass
Mlflow <2.3.1 - Local File Inclusion Bypass
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1.
Template:
id: CVE-2023-2780
info:
name: Mlflow <2.3.1 - Local File Inclusion Bypass
author: iamnoooob,pdresearch
severity: critical
description: |
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1.
impact: |
Successful exploitation could allow an attacker to read sensitive files on the server.
remediation: |
Upgrade Mlflow to version 2.3.1 or later to mitigate the vulnerability.
reference:
- https://huntr.dev/bounties/b12b0073-0bb0-4bd1-8fc2-ec7f17fd7689/
- https://nvd.nist.gov/vuln/detail/CVE-2023-2780
- https://github.com/mlflow/mlflow/commit/fae77a525dd908c56d6204a4cef1c1c75b4e9857
- https://github.com/Ostorlab/KEV
- https://git
No writeups or analysis indexed.
2023-05-17
Published