PyPI package
mlflow
pkg:pypi/mlflow
Vulnerabilities (69)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2024-1594 | Hig | 7.5 | <= 2.9.2 | — | Apr 16, 2024 | 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 rea | |
| CVE-2024-1593 | Hig | 7.5 | <= 2.9.2 | — | Apr 16, 2024 | 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 o | |
| CVE-2024-1560 | Hig | 8.1 | <= 2.9.2 | — | Apr 16, 2024 | 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 | |
| CVE-2024-1558 | Hig | 7.5 | < 2.12.1 | 2.12.1 | Apr 16, 2024 | 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 bypass | |
| CVE-2024-1483 | Hig | 7.5 | < 2.12.1 | 2.12.1 | Apr 16, 2024 | 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 ' | |
| CVE-2024-27133 | Hig | 7.5 | < 2.10.0 | 2.10.0 | Feb 23, 2024 | 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. | |
| CVE-2024-27132 | Hig | 7.5 | < 2.10.0 | 2.10.0 | Feb 23, 2024 | 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. | |
| CVE-2023-6977 | Hig | 7.5 | < 2.9.2 | 2.9.2 | Dec 20, 2023 | This vulnerability enables malicious users to read sensitive files on the server. | |
| CVE-2023-6976 | Hig | 8.8 | < 2.9.2 | 2.9.2 | Dec 20, 2023 | This vulnerability is capable of writing arbitrary files into arbitrary locations on the remote filesystem in the context of the server process. | |
| CVE-2023-6975 | Cri | 9.8 | < 2.9.2 | 2.9.2 | Dec 20, 2023 | A malicious user could use this issue to get command execution on the vulnerable machine and get access to data & models information. | |
| CVE-2023-6974 | Cri | 9.8 | < 2.9.2 | 2.9.2 | Dec 20, 2023 | 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. | |
| CVE-2023-6940 | Hig | 8.8 | < 2.9.2 | 2.9.2 | Dec 19, 2023 | with only one user interaction(download a malicious config), attackers can gain full command execution on the victim system. | |
| CVE-2023-6909 | Hig | 7.5 | < 2.9.2 | 2.9.2 | Dec 18, 2023 | Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2. | |
| CVE-2023-6831 | Hig | 8.1 | < 2.9.2 | 2.9.2 | Dec 15, 2023 | Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2. | |
| CVE-2023-6753 | Hig | 8.8 | < 2.9.2 | 2.9.2 | Dec 13, 2023 | Path Traversal in GitHub repository mlflow/mlflow prior to 2.9.2. | |
| CVE-2023-6709 | Hig | 8.8 | < 2.9.2 | 2.9.2 | Dec 12, 2023 | Improper Neutralization of Special Elements Used in a Template Engine in GitHub repository mlflow/mlflow prior to 2.9.2. | |
| CVE-2023-6568 | Med | 6.1 | < 2.9.0 | 2.9.0 | Dec 7, 2023 | A reflected Cross-Site Scripting (XSS) vulnerability exists in the mlflow/mlflow repository, specifically within the handling of the Content-Type header in POST requests. An attacker can inject malicious JavaScript code into the Content-Type header, which is then improperly refle | |
| CVE-2023-43472 | Hig | 7.5 | < 2.9.0 | 2.9.0 | Dec 5, 2023 | An issue in MLFlow versions 2.8.1 and before allows a remote attacker to obtain sensitive information via a crafted request to REST API. | |
| CVE-2023-6014 | Cri | 9.8 | < 2.8.0 | 2.8.0 | Nov 16, 2023 | An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment. | |
| CVE-2023-6018 | Cri | 9.8 | < 2.9.2 | 2.9.2 | Nov 16, 2023 | An attacker can overwrite any file on the server hosting MLflow without any authentication. |
- affected <= 2.9.2
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 rea
- affected <= 2.9.2
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 o
- affected <= 2.9.2
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
- affected < 2.12.1fixed 2.12.1
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 bypass
- affected < 2.12.1fixed 2.12.1
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 '
- affected < 2.10.0fixed 2.10.0
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.
- affected < 2.10.0fixed 2.10.0
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.
- affected < 2.9.2fixed 2.9.2
This vulnerability enables malicious users to read sensitive files on the server.
- affected < 2.9.2fixed 2.9.2
This vulnerability is capable of writing arbitrary files into arbitrary locations on the remote filesystem in the context of the server process.
- affected < 2.9.2fixed 2.9.2
A malicious user could use this issue to get command execution on the vulnerable machine and get access to data & models information.
- affected < 2.9.2fixed 2.9.2
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.
- affected < 2.9.2fixed 2.9.2
with only one user interaction(download a malicious config), attackers can gain full command execution on the victim system.
- affected < 2.9.2fixed 2.9.2
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.
- affected < 2.9.2fixed 2.9.2
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.
- affected < 2.9.2fixed 2.9.2
Path Traversal in GitHub repository mlflow/mlflow prior to 2.9.2.
- affected < 2.9.2fixed 2.9.2
Improper Neutralization of Special Elements Used in a Template Engine in GitHub repository mlflow/mlflow prior to 2.9.2.
- affected < 2.9.0fixed 2.9.0
A reflected Cross-Site Scripting (XSS) vulnerability exists in the mlflow/mlflow repository, specifically within the handling of the Content-Type header in POST requests. An attacker can inject malicious JavaScript code into the Content-Type header, which is then improperly refle
- affected < 2.9.0fixed 2.9.0
An issue in MLFlow versions 2.8.1 and before allows a remote attacker to obtain sensitive information via a crafted request to REST API.
- affected < 2.8.0fixed 2.8.0
An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment.
- affected < 2.9.2fixed 2.9.2
An attacker can overwrite any file on the server hosting MLflow without any authentication.
Page 3 of 4