Loading vulnerability…
A stack-based buffer overflow vulnerability exists in TUGzip 3.5.0.0. The flaw is triggered when the application processes a .zip archive containing a file with an excessively long filename. This can cause a buffer overflow on the stack, potentially allowing an attacker to execute arbitrary code or cause a denial of service (application crash).
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 (2 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/fileformat/tugzip.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2008-4779) in TugZip version 3.5 for Windows. The exploit works by generating a specially crafted ZIP file (default name: msf.zip) that, when opened with TugZip, triggers the buffer overflow and executes arbitrary code as the victim user. The module uses advanced exploitation techniques, including an egghunter and stack alignment, to deliver a customizable Metasploit payload. The attack vector is local, requiring user interaction (the victim must open the malicious ZIP file). The only fingerprintable endpoint is the generated ZIP file itself. The code is operational and allows for payload customization within the Metasploit 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.