Loading vulnerability…
A stack-based buffer overflow exists in IBM Forms Viewer versions 4.x before 4.0.0.3 and 8.x before 8.0.1.1. The vulnerability is triggered when a user opens a specially crafted XFDL form containing an excessively long fontname value, leading to a buffer overflow on the stack. This can allow remote attackers to execute arbitrary code in the context of the user.
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 single Metasploit module targeting a stack-based buffer overflow vulnerability (CVE-2013-5447) in IBM Forms Viewer 4.0 on Windows XP SP3 and Windows 7 SP1. The exploit works by generating a malicious XFDL file ('msf.xfdl') with an overly long 'fontname' value, which triggers the overflow when opened in the vulnerable application. The module allows the attacker to embed a customizable payload (up to 3000 bytes, Unicode-encoded) that executes with the privileges of the user running IBM Forms Viewer. The exploit is operational and leverages Metasploit's payload framework, with bad character filtering and stack alignment to ensure reliable code execution. The main attack vector is local, requiring user interaction to open the crafted file. The only fingerprintable endpoints are the generated XFDL file and the targeted 'masqform.exe' process within IBM Forms Viewer.
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.