Loading vulnerability…
Zinf 2.2.1 on Windows, along with older Linux versions, contains a buffer overflow when processing certain values in playlist (.pls) files. A remote attacker or local user can use a crafted .pls file to execute arbitrary code.
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 (5 hidden).
This repository contains a single Metasploit module targeting a stack-based buffer overflow vulnerability (CVE-2004-0964) in Zinf Audio Player 2.2.1 for Windows. The exploit generates a malicious .pls (playlist) file that, when opened by a victim in the vulnerable player, triggers a SEH-based buffer overflow, allowing arbitrary code execution. The payload is customizable (up to 800 bytes) and is injected via the overflow. The exploit does not require elevated privileges and is effective when the victim opens the crafted file. The module is written in Ruby and leverages Metasploit's FILEFORMAT and SEH exploitation mixins. The only fingerprintable endpoint is the malicious .pls file itself, and the exploit is operational, providing a working code execution vector for attackers.
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.