First published: Thu May 16 2024(Updated: )
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.
Credit: security@huntr.dev security@huntr.dev
Affected Software | Affected Version | How to fix |
---|---|---|
pip/mlflow | <2.10.1 | 2.10.1 |
MLflow | <2.12.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-4263 is classified as a moderate severity vulnerability due to broken access control allowing low privilege users to delete artifacts.
To fix CVE-2024-4263, upgrade to mlflow version 2.10.1 or later.
CVE-2024-4263 affects mlflow versions prior to 2.10.1.
CVE-2024-4263 is a broken access control vulnerability that allows unauthorized deletion of artifacts.
Low privilege users with EDIT permissions on an experiment can exploit CVE-2024-4263 to delete any artifacts.