← Back
CVE-2024-1594
Path Traversal in mlflow (CVE-2024-1594)
Summary
path traversal in mlflow (CVE-2024-1594). Confidential information can be exposed externally. Exploitable via ``artifact_location``. Mitigation: upgrade to `2.11.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-1594** has been found in mlflow.
Attackers can target a specific entry point like ``artifact_location`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade mlflow to **2.11.3** or later.
If unsure, ask your IT team or search "mlflow CVE-2024-1594" on the vendor's site.
CVE-2024-1594 (mlflow) — CWE-22 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `artifact_location`
Patched: `2.11.3` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in mlflow. Attackers reach the vulnerable code path via ``artifact_location`` without authentication.
📍 Affected scope
mlflow — . Attack surface: `artifact_location`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.11.3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'mlflow' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mlflow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mlflow` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mlflow to 2.11.3ステージング環境で 2.11.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
mlflow
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.11.3"}]}]
PyPI
mlflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.9.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-1594
- advisory https://github.com/advisories/GHSA-m49c-5c52-6696
- package https://github.com/mlflow/mlflow
- package https://pypi.org/project/mlflow
- web https://huntr.com/bounties/424b6f6b-e778-4a2b-b860-39730d396f3e
- web https://github.com/mlflow/mlflow/blob/b929a3e727dc48a1eb19b7e954b7897ac09ad3ec/mlflow/utils/uri.py#L246