Skip to content
Fencer Vulns
critical 10.0

CVE-2004-0964 in the critical feed json

Buffer overflow in Zinf 2.2.1 on Windows, and other older versions for Linux, allows remote attackers or local users to execute arbitrary c…

published 2004-10-20 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0962

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
62.7%
EPSS 62.7% chance of exploitation in 30 days, percentile 99.1%
public exploits
7
Metasploit, Exploit-DB

Summary

Buffer overflow in Zinf 2.2.1 on Windows, and other older versions for Linux, allows remote attackers or local users to execute arbitrary code via certain values in a .pls file.

Patch / fix

Timeline

  1. First public exploit (Metasploit exploit/windows/fileformat/zinfaudioplayer221_pls)
  2. Published

Exploit prediction

62.68% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit exploit/windows/fileformat/zinfaudioplayer221_pls Zinf Audio Player 2.2.1 (PLS File) Stack Buffer Overflow metasploit exploit, good rank, 2004-09-24
  • EDB-17600 Zinf Audio Player 2.2.1 - '.pls' Local Buffer Overflow (DEP Bypass) local, 2011-08-03
  • EDB-16688 Zinf Audio Player 2.2.1 - '.pls' Local Stack Buffer Overflow (Metasploit) local, 2010-11-24
  • EDB-8267 Zinf Audio Player 2.2.1 - '.pls' Universal Overwrite (SEH) local, 2009-03-23
  • EDB-7888 Zinf Audio Player 2.2.1 - '.pls' Universal Local Buffer Overflow local, 2009-01-28
  • EDB-7887 Zinf Audio Player 2.2.1 - '.pls' Stack Overflow (PoC) dos, 2009-01-27
  • EDB-559 Zinf Audio Player 2.2.1 - Local Buffer Overflow local, 2004-09-28
  • securityfocus.com http://www.securityfocus.com/bid/11248 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.