CVE-2024-4263: Improper Access Control in mlflow/mlflow
A broken access control vulnerability exists in mlflow/mlflow versions before 2.10.1, where low privilege users with only EDIT permissions on an experiment can delete any artifacts. This issue arises due to the lack of proper validation for DELETE requests by users with EDIT permissions, allowing them to perform unauthorized deletions of artifacts. The vulnerability specifically affects the handling of artifact deletions within the application, as demonstrated by the ability of a low privilege user to delete a directory inside an artifact using a DELETE request, despite the official documentation stating that users with EDIT permission can only read and update artifacts, not delete them.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/mlflowto a version that resolves this vulnerability.Fixed in 2.10.1 - Upgrade
Upgrade
mlflow/mlflowto a version that resolves this vulnerability.Fixed in 2.10.1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-4263?
CVE-2024-4263 is classified as a moderate severity vulnerability due to broken access control allowing low privilege users to delete artifacts.
How do I fix CVE-2024-4263?
To fix CVE-2024-4263, upgrade to mlflow version 2.10.1 or later.
What versions are affected by CVE-2024-4263?
CVE-2024-4263 affects mlflow versions prior to 2.10.1.
What type of vulnerability is CVE-2024-4263?
CVE-2024-4263 is a broken access control vulnerability that allows unauthorized deletion of artifacts.
Who can exploit CVE-2024-4263?
Low privilege users with EDIT permissions on an experiment can exploit CVE-2024-4263 to delete any artifacts.