Loading vulnerability…
In ImageMagick before version 7.0.8-9, the ReadXBMImage function in coders/xbm.c fails to initialize memory when processing XBM files with negative pixel values. This can result in uninitialized memory being included in the output image data, potentially exposing sensitive information from the process memory if ImageMagick is used as a library within another application.
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 (1 hidden).
This repository provides a proof-of-concept (PoC) exploit for CVE-2018-16323, a memory leakage vulnerability in ImageMagick's XBM image processing. The main script, XBadManners.sh, is a Bash script that can generate malicious XBM image files of arbitrary size and optionally in a minimal format for easier use in web application testing tools. The script also includes a recovery mode that extracts leaked memory from images produced by the vulnerable server after processing the crafted XBM files. The samples directory contains several pre-generated XBM PoC files of various sizes. The exploit targets servers running vulnerable versions of ImageMagick and requires the attacker to upload a crafted XBM file and then download and analyze the resulting image to recover leaked memory. The repository is structured with a main Bash script, a README with detailed usage instructions, and sample payload files. No network endpoints or hardcoded IPs are present; the attack is performed by uploading files to a vulnerable server.
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.