Products / mlflow
mlflow
87 records.
- MLFlow unsafe deserialization Loading a maliciously crafted TensorFlow model through MLflow triggers unsafe deserialisation that runs attacker code on the user's system.
- MLFlow improper input validation A crafted MLproject file passes unfiltered input into execution, so attacker-supplied commands run on the machine that runs the project.
- MLFlow unsafe deserialization A maliciously uploaded PyTorch model in MLflow is deserialised on load, running attacker-chosen code on the machine that interacts with it.
- MLFlow unsafe deserialization A malicious pmdarima model uploaded to MLflow runs arbitrary code on the machine that loads and uses it.
- MLflow allows low privilege users to delete any artifact Users with only edit permission on an experiment can send DELETE requests that remove artifacts, which the documented permissions do not allow.
- MLflow has a Local File Read/Path Traversal bypass A hash fragment in an artifact URL slips past the earlier path check, letting the server resolve and read arbitrary local files.
- mlflow vulnerable to Path Traversal Double URL decoding in artifact deletion lets encoded traversal sequences escape path validation and delete arbitrary server directories.
- mlflow vulnerable to Path Traversal Semicolons in request URLs smuggle path traversal sequences into the params portion, letting attackers reach files outside the intended directory.
- mlflow Path Traversal vulnerability Crafted artifact_location and source values using a '#' local URI bypass insufficient path validation, letting requests read arbitrary server files.
- mlflow vulnerable to Path Traversal Local-path detection mishandles empty or file-scheme URIs, so crafted model version sources are treated as non-local and can read arbitrary files.
- mlflow vulnerable to Path Traversal A crafted source parameter slips past the relative-path check during model version creation, letting attackers read arbitrary server files via the artifact handler.
- mlflow vulnerable to Path Traversal A fragment character in the artifact location makes the server resolve paths past checks meant to stop traversal, reading arbitrary files.
- MLFlow Cross-site Scripting vulnerability leads to client-side Remote Code Execution Dataset table fields are rendered without sanitization, so an untrusted dataset injects script into the notebook view and runs code on the client.
- Cross-site Scripting in MLFlow Running an untrusted MLflow recipe renders template variables without sanitisation, so script injected through them executes in the notebook client.
- MLflow Server-Side Request Forgery (SSRF) Crafted requests make the MLflow server fetch attacker-chosen internal HTTP endpoints, which could lead to code execution on cloud hosts.
- MLflow Path Traversal Vulnerability Filenames containing backslash-dot traversal sequences let a request escape the intended directory and reach other files on the server.
- MLFlow Path Traversal Vulnerability A path traversal flaw in MLflow lets a user reach files outside the intended directory, leading to command execution on the host.
- MLflow Local File Disclosure Vulnerability The MLflow server lets users read arbitrary local files on the host, exposing sensitive server data.
- MLflow Path Traversal Vulnerability The server accepts uploads that write arbitrary files to arbitrary locations on the remote filesystem, using the server process's permissions.
- mlflow Command Injection vulnerability A crafted MLflow configuration file, once downloaded and loaded, injects shell commands that run on the victim's machine.
- Path traversal in MLflow A filename containing backslash-dot sequences escapes the intended directory during file handling in MLflow.
- Path traversal in MLflow Crafted path arguments in MLflow escape the intended directory, letting requests read or write files outside it.
- Jinja2 template injection in mlflow User-controlled content reaches a Jinja2 template without neutralisation, so template expressions can be evaluated and run code on the server.
- Cross-site Scripting (XSS) in MLflow The Content-Type request header is echoed into an HTML response without escaping, so a crafted header runs script in the victim's browser.
- Information exposure in MLflow A crafted request to the MLflow REST API lets a remote attacker retrieve sensitive information from versions up to 2.8.1.
- MLflow authentication requirement bypass can allow a user to arbitrarily create an account A flaw lets an unauthenticated caller create accounts despite the server's requirement that registration be authenticated.
- Remote Code Execution due to Full Controled File Write in mlflow Unrestricted file writes on the MLflow web server let an attacker overwrite files such as shell startup scripts to run commands.
- MLflow allowed arbitrary files to be PUT onto the server MLflow accepts file uploads written to arbitrary server paths without restricting the destination to an allowed directory.
- mlflow vulnerable to OS Command Injection Unsanitised input reaches an operating system command in MLflow builds before 2.6.0, letting an attacker run shell commands.
- MLflow Path Traversal vulnerability Absolute file paths supplied to MLflow are not confined, so crafted input can reach files outside the intended directory.
- mlflow Path Traversal vulnerability An incomplete fix for an earlier MLflow path traversal flaw leaves a bypass that reaches files outside the intended directory.
- mflow vulnerable to directory traversal The MLflow get-artifact endpoint takes an unrestricted path parameter, so traversal sequences let callers read arbitrary files on the server.
- Remote file access vulnerability in `mlflow server` and `mlflow ui` CLIs Older mlflow server and ui releases let remote callers reach arbitrary host files through crafted artifact paths when the server is not access-restricted.
- Relative path traversal in mlflow MLflow before 2.3.1 does not sanitise relative path sequences, letting callers reach files outside the intended directory.
- Remote file existence check vulnerability in `mlflow server` and `mlflow ui` CLIs The MLflow server and UI answer existence queries for arbitrary host files, letting remote clients probe the filesystem.
- mlflow is vulnerable to remote file access in `mlflow server` and `mlflow ui` CLIs A remote caller can request files outside the intended directory from the MLflow server, reading arbitrary host files that the server can access.
- Insecure Temporary File in mlflow Code creates temporary files with the deprecated mktemp function, which returns only a name and leaves a race window for attackers to plant files.