Artifact deletion via reused update permission check
Published May 16, 2024 · Updated Aug 1, 2024
Broken access control in MLflow before 2.10.1 allows remote authenticated users with EDIT permission to delete experiment artifacts. The artifact-proxy DELETE route uses the update-permission validator, whose can_update check accepts EDIT, instead of requiring can_manage. Any account granted EDIT on an experiment can remove files or directories from that experiment's artifact store, causing data loss.
Summary
What happened
Broken access control in MLflow before 2.10.1 allows remote authenticated users with EDIT permission to delete experiment artifacts. The artifact-proxy DELETE route uses the update-permission validator, whose can_update check accepts EDIT, instead of requiring can_manage. Any account granted EDIT on an experiment can remove files or directories from that experiment's artifact store, causing data loss.
The record
- CVE
- CVE-2024-4263
- Published
- May 16, 2024
- Updated
- Aug 1, 2024
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-284, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 16, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <2.10.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Huntr artifact-deletion proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo