| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in mlflow up to 2.2.0. It has been classified as critical. This vulnerability affects unknown code. Performing a manipulation results in path traversal. This vulnerability is cataloged as CVE-2023-1176. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in mlflow up to 2.2.0. It has been classified as critical. This affects an unknown code block. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.2.1.
The weakness was shared 03/24/2023. The advisory is shared at huntr.dev. This vulnerability is uniquely identified as CVE-2023-1176 since 03/04/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Upgrading to version 2.2.1 eliminates this vulnerability. Applying the patch 63ef72aa4334a6473ce7f889573c92fcae0b3c0d is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-0156). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/mlflow/mlflow/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (huntr.dev): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: mlflow 2.2.1
Patch: 63ef72aa4334a6473ce7f889573c92fcae0b3c0d
Timeline
03/04/2023 🔍03/24/2023 🔍
03/24/2023 🔍
07/01/2025 🔍
Sources
Product: github.comAdvisory: 63ef72aa4334a6473ce7f889573c92fcae0b3c0d
Status: Confirmed
CVE: CVE-2023-1176 (🔍)
GCVE (CVE): GCVE-0-2023-1176
GCVE (VulDB): GCVE-100-223809
EUVD: 🔍
Entry
Created: 03/24/2023 18:11Updated: 07/01/2025 14:12
Changes: 03/24/2023 18:11 (40), 04/14/2023 09:27 (1), 04/14/2023 09:31 (21), 07/01/2025 14:12 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.