Bitnami package
mlflow
pkg:bitnami/mlflow
Vulnerabilities (75)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| 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. | |
| CVE-2023-2356 | Hig | 7.5 | < 2.3.1 | 2.3.1 | Apr 28, 2023 | Relative Path Traversal in GitHub repository mlflow/mlflow prior to 2.3.1. | |
| CVE-2023-1177 | Cri | 9.3 | < 2.2.1 | 2.2.1 | Mar 24, 2023 | Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.2.1. | |
| CVE-2023-1176 | Low | 3.3 | < 2.2.2 | 2.2.2 | Mar 24, 2023 | Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.2.2. | |
| CVE-2022-0736 | Hig | 7.5 | < 1.23.1 | 1.23.1 | Feb 23, 2022 | Insecure Temporary File in GitHub repository mlflow/mlflow prior to 1.23.1. |
- 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.
- affected < 2.3.1fixed 2.3.1
Relative Path Traversal in GitHub repository mlflow/mlflow prior to 2.3.1.
- affected < 2.2.1fixed 2.2.1
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.2.1.
- affected < 2.2.2fixed 2.2.2
Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.2.2.
- affected < 1.23.1fixed 1.23.1
Insecure Temporary File in GitHub repository mlflow/mlflow prior to 1.23.1.
Page 4 of 4