Vulnerabilities · 2024 · Lfprojects
CVE-2024-4263
Lfprojects Mlflow vulnerability
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 products
Mlflow. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Lfprojects Mlflow runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/mlflow/mlflow/commit/b43e0e3de5b500554e13dc032ba2083b2d6c94b8 · Patch
- huntr.com/bounties/bfa116d3-2af8-4c4a-ac34-ccde7491ae11 · Exploit
- nvd.nist.gov/vuln/detail/CVE-2024-4263
- github.com/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2024-51.yaml
- github.com/advisories/GHSA-p4jx-q62p-x5jr
- nvd.nist.gov/vuln/detail/CVE-2024-4263
- cve.org/CVERecord?id=CVE-2024-4263
More vulnerabilities in Lfprojects products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.