CVE-2009-4962 in the critical feed json
Stack-based buffer overflow in Fat Player 0.6b allows remote attackers to execute arbitrary code via a long string in a .wav file.
published 16y ago modified 4mo ago also EUVD-2009-4924
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 31.4%
- EPSS 31.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 4
- Metasploit and Exploit-DB
Summary
Stack-based buffer overflow in Fat Player 0.6b allows remote attackers to execute arbitrary code via a long string in a .wav file. NOTE: some of these details are obtained from third party information.
Is CVE-2009-4962 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-9495)
- Published
Exploit prediction
31.38% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/fileformat/fatplayer_wav Fat Player Media Player 0.6b0 Buffer Overflow metasploit exploit, normal rank, 2010-10-18
- EDB-15279 Fat Player 0.6b - '.wav' Local Buffer Overflow (SEH) local, 2010-10-18
- EDB-14591 Fat Player 0.6b - '.WAV' File Processing Buffer Overflow (SEH) local, 2010-08-09
- EDB-9495 Fat Player 0.6b - '.wav' Universal Local Buffer local, 2009-08-24
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/9495
exploit
-
vupen.com
/english/advisories/2009/2394
vdb-entry, vendor-advisory
-
secunia.com
/advisories/36441
third-party-advisory, vendor-advisory
-
osvdb.org
/57343
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/52713
vdb-entry
Sources
- CVE List CVE-2009-4962
- NVD CVE-2009-4962
Fencer Intel 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.