Loading vulnerability…
A vulnerability in Ghostscript versions prior to 9.50 affects the .pdf_hook_DSC_Creator procedure. The flaw stems from improper securing of privileged calls, allowing a specially crafted PostScript file to bypass the intended restrictions enforced by the -dSAFER security mode. By disabling or circumventing these protections, an attacker can cause Ghostscript to access the local file system and execute arbitrary commands, defeating the sandboxing model intended to constrain untrusted PostScript content.
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-2019-14811, a vulnerability in GhostScript that allows bypassing the 'Safer' mode and executing arbitrary shell commands. The exploit is implemented as a single PostScript file ('exploit.ps'), which leverages the '.pdf_hook_DSC_Creator' operator to obtain the '.forceput' operator, then disables security flags and executes a shell command (demonstrated with 'id'). The README provides context and credits prior research. The exploit targets environments where GhostScript is used to render PDF previews, such as in web applications that generate image previews from uploaded PDFs. The main attack vector is local, as the exploit requires the target to process a malicious PostScript file. The only code file is 'exploit.ps', and the repository is structured as a minimal PoC with clear 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.
2 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.