Bitnami package
mlflow
pkg:bitnami/mlflow
Vulnerabilities (84)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| 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 | >= 1.0.0, < 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.1 | 2.9.1 | 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.8.2 | 2.8.2 | 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 | — | — | Nov 16, 2023 | An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment. | |
| CVE-2023-6018 | Cri | 9.8 | — | — | Nov 16, 2023 | An attacker can overwrite any file on the server hosting MLflow without any authentication. | |
| CVE-2023-6015 | Hig | 7.5 | < 2.8.1 | 2.8.1 | Nov 16, 2023 | MLflow allowed arbitrary files to be PUT onto the server. | |
| CVE-2023-4033 | Hig | 7.8 | < 2.6.0 | 2.6.0 | Aug 1, 2023 | OS Command Injection in GitHub repository mlflow/mlflow prior to 2.6.0. | |
| CVE-2023-3765 | Cri | 10.0 | < 2.5.0 | 2.5.0 | Jul 19, 2023 | Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0. | |
| CVE-2023-2780 | Cri | 9.8 | < 2.3.1 | 2.3.1 | May 17, 2023 | Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1. | |
| CVE-2023-30172 | Hig | 7.5 | < 2.0.1 | 2.0.1 | May 11, 2023 | A directory traversal vulnerability in the /get-artifact API method of the mlflow platform up to v2.0.1 allows attackers to read arbitrary files on the server via the path parameter. |
- 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 >= 1.0.0, < 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.1fixed 2.9.1
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.8.2fixed 2.8.2
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.
An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment.
An attacker can overwrite any file on the server hosting MLflow without any authentication.
- affected < 2.8.1fixed 2.8.1
MLflow allowed arbitrary files to be PUT onto the server.
- affected < 2.6.0fixed 2.6.0
OS Command Injection in GitHub repository mlflow/mlflow prior to 2.6.0.
- affected < 2.5.0fixed 2.5.0
Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.
- affected < 2.3.1fixed 2.3.1
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.3.1.
- affected < 2.0.1fixed 2.0.1
A directory traversal vulnerability in the /get-artifact API method of the mlflow platform up to v2.0.1 allows attackers to read arbitrary files on the server via the path parameter.
Page 4 of 5