Skip to content
Fencer Vulns
high 7.5

CVE-2006-6199 in the critical feed json

Stack-based buffer overflow in BlazeVideo BlazeDVD Standard and Professional 5.0, and possibly earlier, allows remote attackers to execute…

published 2006-12-01 19 y ago modified 2026-06-16 4 mo ago also EUVD-2006-6182

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
66.3%
EPSS 66.3% chance of exploitation in 30 days, percentile 99.2%
public exploits
10
Metasploit, Exploit-DB

Summary

Stack-based buffer overflow in BlazeVideo BlazeDVD Standard and Professional 5.0, and possibly earlier, allows remote attackers to execute arbitrary code via a long filename in a PLF playlist.

Timeline

  1. First public exploit (EDB-2880)
  2. Published

Exploit prediction

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

Exploits and checks

  • Metasploit exploit/windows/fileformat/blazedvd_plf BlazeDVD 6.1 PLF Buffer Overflow metasploit exploit, good rank, 2009-08-03
  • EDB-29263 BlazeDVD 6.2 - '.plf' Local Buffer Overflow (SEH) local, 2013-10-28
  • EDB-26889 BlazeDVD Pro Player 6.1 - Direct RET Local Stack Buffer Overflow local, 2013-07-16
  • EDB-23783 BlazeDVD 6.1 - '.PLF' File (ASLR + DEP Bypass) (Metasploit) local, 2012-12-31
  • EDB-16618 BlazeDVD 5.1 - PLF Buffer Overflow (Metasploit) local, 2010-11-11
  • EDB-13905 BlazeDVD 5.1 (Windows 7) - '.plf' File Stack Buffer Overflow (ASLR + DEP Bypass) local, 2010-06-17
  • EDB-9360 BlazeDVD 5.1/HDTV Player 6.0 - '.plf' Universal Buffer Overflow (SEH) local, 2009-08-04
  • EDB-9329 BlazeDVD 5.1 Professional - '.plf' Local Buffer Overflow (SEH) local, 2009-08-03
  • EDB-6217 BlazeDVD 5.0 - '.PLF' Playlist File Remote Buffer Overflow remote, 2008-08-10
  • EDB-2880 BlazeVideo HDTV Player 2.1 - '.PLF' Local Buffer Overflow local, 2006-12-01

CVSS scores

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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.