CVE-2023-30172
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA directory traversal vulnerability exists in the /get-artifact API endpoint of mlflow where the path parameter is not properly sanitized, allowing attackers to use '../' sequences to escape the intended artifact directory and read arbitrary files on the server's filesystem.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if mlflow is installedRun 'pip show mlflow' or 'python -c "import mlflow; print(mlflow.__version__)"'Affected if mlflow is not installed or version cannot be determined
-
Verify installed mlflow versionCompare the version from step 1 against the affected range (< 2.0.1)Affected if installed version is lower than 2.0.1
-
Determine if mlflow server is runningCheck for running mlflow processes or check if port 5000 (default mlflow server port) is listening: 'ps aux | grep mlflow' or 'netstat -tlnp | grep 5000'Affected if mlflow server is running and the artifact API is accessible over network
-
Confirm /get-artifact endpoint exposureCheck mlflow server configuration or test accessing the endpoint via curl http://localhost:5000/api/2.0/mlflow-artifacts/get-artifact?path=test (note: this is informational only)Affected if the /get-artifact API endpoint is accessible and the mlflow version is < 2.0.1
You are affected if mlflow version is below 2.0.1 AND the /get-artifact API endpoint is exposed and accessible in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.1
Upgrade mlflow to version v2.0.2 or later, which contains the fix for this path traversal vulnerability. If immediate patching is not possible, implement input validation on the path parameter to reject sequences containing '../' and ensure all file access is restricted to the designated artifact storage directory.
mlflow >= 2.0.1
- Check current mlflow version using: pip show mlflow or mlflow --version
- Upgrade mlflow to version 2.0.1 or later using: pip install --upgrade mlflow>=2.0.1
- Verify the upgrade was successful: pip show mlflow | grep Version
- Restart any running mlflow servers (mlflow ui, mlflow server) to ensure the patched version is loaded
- Test that the /get-artifact API no longer allows path traversal by attempting to access a file outside the intended artifact directory (e.g., /get-artifact?path=../../../../etc/passwd should fail)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30172 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data