Loading vulnerability…
A command injection vulnerability exists in ExifTool prior to version 12.38, specifically in the lib/Image/ExifTool.pm module. The vulnerability arises from improper handling of file names, where the check $file =~ /|$/ is insufficient to prevent shell metacharacter injection, allowing an attacker to execute arbitrary commands via crafted file names.
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 Python-based exploit for CVE-2022-23935, a command injection vulnerability in ExifTool versions prior to 12.38. The exploit generates a staged reverse shell payload by creating a specially crafted JPEG file whose filename contains a command to fetch and execute a shell from the attacker's server. The main logic resides in 'src/cve_2022_23935/main.py', which handles argument parsing, payload generation, and serving the payload over HTTP. The exploit requires the attacker to specify their IP and port for the reverse shell callback, and optionally the shell type and server listen port. The tool then creates a JPEG file with a malicious filename and starts an HTTP server to deliver the payload. When the vulnerable ExifTool instance processes the file, it triggers a reverse shell to the attacker's machine. The repository is structured as a Python package with a CLI entry point, and includes standard project files such as a README, LICENSE, and pyproject.toml. No hardcoded IPs or domains are present; all endpoints are user-supplied at runtime.
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.