Steinberg MyMP3Player up to 3.0.0.67 m3u Playlist File Parser stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Steinberg MyMP3Player up to 3.0.0.67. Affected is an unknown function of the component m3u Playlist File Parser. This manipulation causes stack-based overflow. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is handled as CVE-2010-20123. The attack can be initiated remotely. Additionally, an exploit exists.
Details
A vulnerability was found in Steinberg MyMP3Player up to 3.0.0.67. It has been declared as critical. Affected by this vulnerability is some unknown functionality of the component m3u Playlist File Parser. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Steinberg MyMP3Player version 3.0 (build 3.0.0.67) is vulnerable to a stack-based buffer overflow when parsing .m3u playlist files. The application fails to properly validate the length of input data within the playlist, allowing a specially crafted file to overwrite critical memory structures and execute arbitrary code. This vulnerability can be exploited locally by convincing a user to open a malicious .m3u file.
The weakness was released by n3w7u as 11791. The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2010-20123 since 08/20/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available.
It is possible to download the exploit at exploit-db.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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 3.0.0.0
- 3.0.0.1
- 3.0.0.2
- 3.0.0.3
- 3.0.0.4
- 3.0.0.5
- 3.0.0.6
- 3.0.0.7
- 3.0.0.8
- 3.0.0.9
- 3.0.0.10
- 3.0.0.11
- 3.0.0.12
- 3.0.0.13
- 3.0.0.14
- 3.0.0.15
- 3.0.0.16
- 3.0.0.17
- 3.0.0.18
- 3.0.0.19
- 3.0.0.20
- 3.0.0.21
- 3.0.0.22
- 3.0.0.23
- 3.0.0.24
- 3.0.0.25
- 3.0.0.26
- 3.0.0.27
- 3.0.0.28
- 3.0.0.29
- 3.0.0.30
- 3.0.0.31
- 3.0.0.32
- 3.0.0.33
- 3.0.0.34
- 3.0.0.35
- 3.0.0.36
- 3.0.0.37
- 3.0.0.38
- 3.0.0.39
- 3.0.0.40
- 3.0.0.41
- 3.0.0.42
- 3.0.0.43
- 3.0.0.44
- 3.0.0.45
- 3.0.0.46
- 3.0.0.47
- 3.0.0.48
- 3.0.0.49
- 3.0.0.50
- 3.0.0.51
- 3.0.0.52
- 3.0.0.53
- 3.0.0.54
- 3.0.0.55
- 3.0.0.56
- 3.0.0.57
- 3.0.0.58
- 3.0.0.59
- 3.0.0.60
- 3.0.0.61
- 3.0.0.62
- 3.0.0.63
- 3.0.0.64
- 3.0.0.65
- 3.0.0.66
- 3.0.0.67
Support
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/20/2025 CVE reserved08/21/2025 Advisory disclosed
08/21/2025 VulDB entry created
08/21/2025 VulDB entry last update
Sources
Advisory: 11791Researcher: n3w7u
Status: Not defined
CVE: CVE-2010-20123 (🔒)
GCVE (CVE): GCVE-0-2010-20123
GCVE (VulDB): GCVE-100-321001
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/21/2025 22:48Changes: 08/21/2025 22:48 (71)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.