A buffer overflow vulnerability exists in Poster Software PUBLISH-iT version 3.6d. The vulnerability can be triggered by a remote attacker supplying a specially crafted PUI file, which causes a buffer overflow condition in the application. This may allow the attacker to execute arbitrary code in the context of the user running the 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 (3 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/fileformat/publishit_pui.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2014-0980) in Publish-It 3.6d for Windows. The exploit works by generating a specially crafted .PUI file that, when opened by a victim in the vulnerable application, triggers a buffer overflow via SEH overwrite, allowing arbitrary code execution. The module allows the attacker to specify a payload, which is encoded and embedded into the malicious file. The exploit is operational and requires user interaction (the victim must open the file). The only fingerprintable endpoints are the malicious .PUI file generated (default name 'msf.pui') and the template file used ('CVE-2014-0980.pui'). The code is written in Ruby and is structured as a standard Metasploit file format exploit module.
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.