Platform
python
Component
mlflow
Fixed in
2.8.1
CVE-2023-6015 describes a critical Arbitrary File Access vulnerability present in MLflow versions up to 2.8.0. This flaw allows attackers to upload arbitrary files to the MLflow server, posing a significant risk to data integrity and system security. The vulnerability has been resolved in version 2.8.1, and users are strongly advised to upgrade immediately.
The Arbitrary File Access vulnerability in MLflow allows an attacker to upload any file they choose to the MLflow server. This could be exploited to upload malicious code, such as a web shell, which would grant the attacker remote code execution capabilities. Alternatively, attackers could overwrite critical configuration files, disrupting MLflow's functionality or gaining access to sensitive data stored within the system. The potential impact extends beyond the MLflow instance itself, as a compromised server could be used as a pivot point for lateral movement within the network, potentially affecting other connected systems and data stores. The ability to upload arbitrary files bypasses standard security controls and represents a severe compromise of the system's integrity.
CVE-2023-6015 was publicly disclosed on November 16, 2023. While no active exploitation campaigns have been publicly confirmed, the CRITICAL severity and ease of exploitation make it a high-priority vulnerability. There are currently no known public proof-of-concept exploits, but the vulnerability's nature suggests that such exploits are likely to emerge. This vulnerability is not currently listed on the CISA KEV catalog.
Exploit Status
EPSS
0.77% (73% percentile)
CVSS Vector
The primary mitigation for CVE-2023-6015 is to upgrade MLflow to version 2.8.1 or later, which contains the fix for this vulnerability. If upgrading immediately is not feasible, consider implementing temporary workarounds such as restricting file upload permissions on the MLflow server and closely monitoring file system activity for suspicious uploads. Implement a Web Application Firewall (WAF) with rules to block attempts to upload files to the MLflow API endpoints. Regularly scan the MLflow server for unauthorized files and review access controls to ensure only authorized users can upload files. After upgrading, confirm the fix by attempting a file upload via the MLflow API and verifying that the upload is rejected.
Update MLflow to the latest available version. This will resolve the arbitrary file upload vulnerability. See the release notes for more details about the update.
Vulnerability analysis and critical alerts directly to your inbox.
CVE-2023-6015 is a CRITICAL vulnerability in MLflow versions up to 2.8.0 that allows attackers to upload arbitrary files to the server, potentially leading to code execution or data compromise.
Yes, if you are using MLflow version 2.8.0 or earlier, you are affected by this vulnerability.
Upgrade MLflow to version 2.8.1 or later to remediate the vulnerability. Consider temporary workarounds like restricting file upload permissions if immediate upgrade is not possible.
While no active exploitation campaigns have been publicly confirmed, the CRITICAL severity and ease of exploitation make it a high-priority vulnerability.
Refer to the MLflow security advisory for detailed information and updates: [https://mlflow.org/docs/security](https://mlflow.org/docs/security)
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Upload your requirements.txt file and we'll tell you instantly if you're affected.