CVE-2009-4756 json
Stack-based buffer overflow in TraktorBeatport.exe 1.0.0.283 in Beatport Player 1.0.0.0 allows remote attackers to execute arbitrary code v…
published 16y ago modified 4mo ago also EUVD-2009-4720
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.9%
- EPSS 6.9% chance of exploitation in 30 days, percentile 94%
- public exploits
- 4
- Exploit-DB
Summary
Stack-based buffer overflow in TraktorBeatport.exe 1.0.0.283 in Beatport Player 1.0.0.0 allows remote attackers to execute arbitrary code via a long string in a malformed playlist (.m3u) file.
Is CVE-2009-4756 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-8592)
- Published
Exploit prediction
6.86% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-8592 Beatport Player 1.0.0.283 - '.m3u' Local Stack Overflow (3) local, 2009-05-01
- EDB-8591 Beatport Player 1.0.0.283 - '.m3u' Local Stack Overflow (2) local, 2009-05-01
- EDB-8590 Beatport Player 1.0.0.283 - '.m3u' Local Overwrite (SEH) local, 2009-05-01
- EDB-8588 Beatport Player 1.0.0.283 - '.m3u' Local Buffer Overflow (PoC) dos, 2009-05-01
- securityfocus.com http://www.securityfocus.com/bid/34793 referenced PoC, tagged "exploit" by a source, unverified
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/8588
exploit
-
exploit-db.com
/exploits/8592
exploit
-
exploit-db.com
/exploits/8590
exploit
-
exploit-db.com
/exploits/8591
exploit
-
securityfocus.com
/bid/34793
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/50267
vdb-entry
Sources
- CVE List CVE-2009-4756
- NVD CVE-2009-4756
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.