| CVE-2024-37052 | CAO8.8 | Deserialization of untrusted data can occur in versions of the MLflow platform running version 1.1.0 or newer, enabling a maliciously uploaded scikit-learn model to run arbitrary code on an end user’s system when interacted with. | 04/06/2024 |
| CVE-2024-4263 | TRUNG BÌNH5.4 | 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 unauth | 16/05/2024 |
| CVE-2024-3848 | CAO7.5 | A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909. The vulnerability arises from the application's handling of artifact URLs, where a '#' character can be used to insert a path into the fragment, effectively skipping validation. This | 16/05/2024 |
| CVE-2024-3573 | NGHIÊM TRỌNG9.3 | mlflow/mlflow is vulnerable to Local File Inclusion (LFI) due to improper parsing of URIs, allowing attackers to bypass checks and read arbitrary files on the system. The issue arises from the 'is_local_uri' function's failure to properly handle URIs with empty or 'file' schemes, leading to the misclassification of URI | 16/04/2024 |
| CVE-2024-1594 | CAO7.5 | A path traversal vulnerability exists in the mlflow/mlflow repository, specifically within the handling of the `artifact_location` parameter when creating an experiment. Attackers can exploit this vulnerability by using a fragment component `#` in the artifact location URI to read arbitrary files on the server in the c | 16/04/2024 |
| CVE-2024-1593 | CAO7.5 | A path traversal vulnerability exists in the mlflow/mlflow repository due to improper handling of URL parameters. By smuggling path traversal sequences using the ';' character in URLs, attackers can manipulate the 'params' portion of the URL to gain unauthorized access to files or directories. This vulnerability allows | 16/04/2024 |
| CVE-2024-1560 | CAO8.1 | A path traversal vulnerability exists in the mlflow/mlflow repository, specifically within the artifact deletion functionality. Attackers can bypass path validation by exploiting the double decoding process in the `_delete_artifact_mlflow_artifacts` handler and `local_file_uri_to_path` function, allowing for the deleti | 16/04/2024 |
| CVE-2024-1558 | CAO7.5 | A path traversal vulnerability exists in the `_create_model_version()` function within `server/handlers.py` of the mlflow/mlflow repository, due to improper validation of the `source` parameter. Attackers can exploit this vulnerability by crafting a `source` parameter that bypasses the `_validate_non_local_source_conta | 16/04/2024 |
| CVE-2024-1483 | CAO7.5 | A path traversal vulnerability exists in mlflow/mlflow version 2.9.2, allowing attackers to access arbitrary files on the server. By crafting a series of HTTP POST requests with specially crafted 'artifact_location' and 'source' parameters, using a local URI with '#' instead of '?', an attacker can traverse the server' | 16/04/2024 |
| CVE-2024-27133 | NGHIÊM TRỌNG9.6 | Insufficient sanitization in MLflow leads to XSS when running a recipe that uses an untrusted dataset. This issue leads to a client-side RCE when running the recipe in Jupyter Notebook. The vulnerability stems from lack of sanitization over dataset table fields. | 23/02/2024 |
| CVE-2024-27132 | NGHIÊM TRỌNG9.6 | Insufficient sanitization in MLflow leads to XSS when running an untrusted recipe.
This issue leads to a client-side RCE when running an untrusted recipe in Jupyter Notebook.
The vulnerability stems from lack of sanitization over template variables.
| 23/02/2024 |
| CVE-2023-6977 | CAO7.5 | This vulnerability enables malicious users to read sensitive files on the server. | 20/12/2023 |
| CVE-2023-6976 | CAO8.8 | This vulnerability is capable of writing arbitrary files into arbitrary locations on the remote filesystem in the context of the server process. | 20/12/2023 |
| CVE-2023-6975 | NGHIÊM TRỌNG9.8 | A malicious user could use this issue to get command execution on the vulnerable machine and get access to data & models information. | 20/12/2023 |
| CVE-2023-6974 | NGHIÊM TRỌNG9.8 | A malicious user could use this issue to access internal HTTP(s) servers and in the worst case (ie: aws instance) it could be abuse to get a remote code execution on the victim machine. | 20/12/2023 |
| CVE-2023-6940 | CAO8.8 | with only one user interaction(download a malicious config), attackers can gain full command execution on the victim system. | 19/12/2023 |
| CVE-2023-6909 | CAO7.5 | Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2. | 18/12/2023 |
| CVE-2023-6831 | CAO8.1 | Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2. | 15/12/2023 |
| CVE-2023-6753 | CAO8.8 | Path Traversal in GitHub repository mlflow/mlflow prior to 2.9.2. | 13/12/2023 |
| CVE-2023-6709 | CAO8.8 | Improper Neutralization of Special Elements Used in a Template Engine in GitHub repository mlflow/mlflow prior to 2.9.2. | 12/12/2023 |