Loading vulnerability…
pdfmake 0.2.9 exposes a /pdf endpoint through an externally installed test framework that can execute arbitrary code when it receives a crafted POST request. The issue is disputed because the endpoint behavior is intentional and the test framework is outside the pdfmake application; deployment operators are responsible for limiting the endpoint to authorized testers.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python exploit script (CVE-2024-25180.py) and a README.md describing the vulnerability and usage. The exploit targets CVE-2024-25180, a remote code execution vulnerability in pdfmake, a JavaScript PDF generation library. The script sends a crafted JSON payload to the /pdf endpoint of a vulnerable pdfmake server, injecting JavaScript that executes a bash reverse shell command via Node.js's child_process module. The attacker receives a shell on their machine by listening on the specified local port. The exploit requires the attacker to know the target's IP and port, as well as to have a listener ready for the reverse shell. The main attack vector is network-based, exploiting an HTTP POST endpoint. The repository is straightforward, with a single exploit script and documentation.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.