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.
Security readout for executives and security teams
Plain-English summary
This is a user-assisted desktop application flaw. If a user opens a malicious M3U playlist in Steinberg MyMP3Player 3.0 build 3.0.0.67, the application can crash or run attacker-controlled code with that user’s privileges.
Executive priority
Treat as high priority only where the application is present. The main business risk is compromise from a malicious file opened by a user, not internet-wide remote exposure.
Technical view
The CVE describes a stack-based buffer overflow in MyMP3Player playlist parsing, classified as CWE-121. CVSS 4.0 scores it 8.4 with local attack vector, low complexity, no privileges required, and active user interaction required.
Likely exposure
Exposure is likely limited to endpoints running the legacy MyMP3Player application, especially where M3U files are opened from email, web downloads, or shared storage. The source bundle has no CPEs, so CPE-based scanners may miss it.
Exploitation context
The source bundle cites public exploit references, including Exploit-DB entries and a Metasploit file-format module. However, KEV is false and no provided source states active in-the-wild exploitation.
Researcher notes
There is a metadata inconsistency: the description names MyMP3Player 3.0 build 3.0.0.67, while the affected entry lists version 0 and defaultStatus unaffected. Validate against installed software evidence before broad remediation.
Mitigation direction
Inventory and remove MyMP3Player where there is no business need.
Do not open M3U playlists from untrusted sources.
Check vendor or trusted distributor guidance for fixed versions or retirement advice.
Restrict file associations so M3U files do not open in MyMP3Player.
Use email and web filtering to quarantine suspicious playlist attachments.
Validation and detection
Identify endpoints with MyMP3Player 3.0 build 3.0.0.67 installed.
Check whether M3U files are associated with MyMP3Player.
Review EDR and download telemetry for suspicious M3U files.
Confirm FortiGuard IPS coverage if Fortinet inspection is deployed.
Prioritize systems used by staff likely to handle media files.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.