pdf_info version 0.5.3 is vulnerable to command execution due to the use of Ruby backticks for executing system commands instead of the safer Open3 module. This allows attackers to inject arbitrary commands if user input is passed to the vulnerable code path.
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 demonstrates a proof-of-concept (POC) exploit for CVE-2022-36231, a command injection vulnerability in the Ruby gem pdf_info (<= 0.5.3). The vulnerability arises from unsanitized user input being passed to a shell command when instantiating a PDF::Info object with a crafted file path. The repository contains two files: a README.md with detailed vulnerability analysis and exploitation steps, and poc.rb, a Ruby script that demonstrates both benign and malicious usage. The malicious example injects a reverse shell payload via the PDF file path, connecting back to 127.0.0.1:4444. The exploit requires the target to use the vulnerable gem and process attacker-controlled file paths. The payload is a bash reverse shell, and the attack vector is local (user-supplied file path). The repository is a clear, functional POC and does not use any exploit framework.
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.