Loading vulnerability…
CVE-2023-1177 is a path traversal vulnerability in MLflow static file serving prior to version 2.2.1. The flaw involves traversal input using a backslash-dot-dot-backslash sequence followed by a filename, which can cause file-path handling to escape the intended directory restriction.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a Proof-of-Concept (PoC) exploit for CVE-2023-1177, a Local File Inclusion (LFI) vulnerability in MLflow versions <=2.1.1. The vulnerability exists in the 'GET /model-versions/get-artifact' endpoint, which fails to properly validate file paths when a model version is created with a malicious 'source' URI (such as file:///). The provided Python script (exp.py) automates the exploitation process: it registers a new model, creates a model version with a malicious source, and then requests an arbitrary file via the vulnerable endpoint. The exploit is operational against MLflow servers accessible over HTTP and can be used to read any file on the server's filesystem that the MLflow process user can access. The repository includes environment setup files (environment.yml) to ensure the correct dependencies are installed for testing. The main exploit logic is contained in exp.py, which is the primary entry point for exploitation. The rest of the repository contains a full copy of the MLflow 2.1.1 source tree, but the exploit is independent and does not require modification of the MLflow codebase.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An MLflow path traversal vulnerability in static file serving, mentioned only in passing in the vendor security history section.
A path traversal vulnerability in MLflow static file serving mentioned as part of vendor security history.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.