Beatport Beatport Player 1.0.0.0 TraktorBeatport.exe memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Beatport Beatport Player 1.0.0.0. This impacts an unknown function of the file TraktorBeatport.exe. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2009-4756. In addition, an exploit is available.
Details
A vulnerability was found in Beatport Beatport Player 1.0.0.0. It has been classified as critical. This affects an unknown code of the file TraktorBeatport.exe. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was presented 03/29/2010 by rgod (Website). The advisory is shared at milw0rm.com. This vulnerability is uniquely identified as CVE-2009-4756 since 03/29/2010. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
A public exploit has been developed in Python. The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (50267), Exploit-DB (8588) and SecurityFocus (BID 34793†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.1
VulDB Base Score: 10.0
VulDB Temp Score: 9.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 800749
OpenVAS Name: Beatport Player .m3u File Buffer Overflow Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/01/2009 🔍03/29/2010 🔍
03/29/2010 🔍
03/29/2010 🔍
03/19/2015 🔍
05/03/2026 🔍
Sources
Advisory: milw0rm.com⛔Researcher: rgod
Status: Not defined
CVE: CVE-2009-4756 (🔍)
GCVE (CVE): GCVE-0-2009-4756
GCVE (VulDB): GCVE-100-52413
X-Force: 50267 - Beatport Player .M3U buffer overflow
SecurityFocus: 34793 - Beatport Player '.m3u' File Remote Stack Buffer Overflow Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/19/2015 12:22Updated: 05/03/2026 16:16
Changes: 03/19/2015 12:22 (55), 12/27/2017 09:17 (8), 11/28/2024 17:09 (16), 05/03/2026 16:16 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.