CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NHigh (7.5) in lfprojects mlflow. EPSS 4.1% estimated probability of exploitation activity in the next 30 days. Fixed in mlflow 2.3.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:Nmlflow (PyPI): fixed in 2.3.1Explain CVE-2023-2356 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-2356?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-2356?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-2356 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| mlflow/mlflow | before 2.3.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-x422-6qhv-p29g | PyPI | mlflow | <2.3.1 | 2.3.1 |
| PYSEC-2023-68 | PyPI | mlflow | <2.3.1 | 2.3.1 |
Red Hat rates this Important.
This vulnerability is rated as Important for Red Hat environments running MLflow tracking servers, because an unauthenticated remote attacker can exploit improper path resolution to access and manipulate sensitive files outside the intended storage directories. Because tracking servers are often deployed to coordinate machine learning workloads across distributed nodes, exposing the service without network perimeter controls allows arbitrary read and write operations on the underlying host filesystem. This widespread potential for complete confidentiality and integrity compromise without requiring user interaction justifies the critical rating.
Restrict network access to the MLflow tracking server so that it is accessible only from trusted administrative networks or localhost. If MLflow is hosted on Red Hat Enterprise Linux, firewall rules can be configured to block untrusted external traffic to the service port (default TCP 5000):
# firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_CIDR>
# firewall-cmd --permanent --zone=public --remove-port=5000/tcp
# firewall-cmd --reload
Caveats: Restricting network reachability prevents unauthorized or external clients from querying metrics or logging artifacts. Applying firewall configuration changes via reload may temporarily disrupt active network connections.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-mlflow-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cpu-torch210-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-cuda130-torch210-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th06-rocm64-torch291-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th-torch-cpu-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th-torch-cuda-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-th-torch-rocm-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-training-cuda128-torch29-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9 | Not affected | |
| Red Hat OpenShift AI (RHOAI) | rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9 | Not affected | |
| 2 more in the JSON and on Red Hat's page. | |||
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-2356.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.