Loading vulnerability…
CVE-2024-21545 is an arbitrary file read vulnerability in Proxmox Virtual Environment (Proxmox VE). The vulnerability arises from insufficient validation of API response values in the handle_api2_request function. Specifically, if a request handler's response includes a 'download' or 'data'->'download' object, the function will read and return a local file specified by this object. Two API endpoints allow authenticated users with 'Sys.Audit' or 'VM.Monitor' privileges to control this object, enabling them to read arbitrary files from the host system.
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 contains a proof-of-concept exploit for CVE-2024-21545, targeting Proxmox VE. The exploit is implemented in a single Python script (poc/poc.py) and demonstrates two attack vectors: (1) using a malicious qemu-guest-agent in a VM to read arbitrary files from the Proxmox host (requiring VM.Monitor privilege and root in the VM), and (2) abusing the ACME meta endpoint to read files as www-data (requiring Sys.Audit privilege). The script authenticates to the Proxmox API, checks permissions, attempts to read sensitive files (such as /etc/shadow and authentication keys), forges a root session using stolen keys, and verifies root access. The exploit leverages several Proxmox API endpoints over HTTPS and uses an external service (httpbingo.org) for the ACME vector. The repository structure is simple, with a README and the main exploit script. The exploit is operational and demonstrates full system compromise if the required conditions are met.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.