MLFLOW · CVE-2023-6015 · Package
FIX → 2.8.1
MLflow, a machine learning tracking library, allowed files to be uploaded to arbitrary locations on the server through a crafted request path. An attacker who can reach the server can write files anywhere the MLflow process has permission, which can lead to code execution.
first public Nov 16, 2023 · 1 public exploit · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run an MLflow tracking server reachable over a network, where the artifact upload endpoints accept requests. Local notebook use on a single machine that does not expose a server is less exposed. Teams on mlflow 2.8.1 or later are not affected.
Not affected if managed-hosting, version-2.8.1-or-later
Who cares mlflow, python, self-hosted
pip show mlflow; versions below 2.8.1 are affected.Upgrade to 2.8.1
MLflow allowed arbitrary files to be PUT onto the server.
This page as .md · .json · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
mlflow to 2.8.1 or later.