dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2010-10016

CRITICAL · 10.0 CVSS v4.0 Published 2025-08-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
BS.Player version 2.57 (build 1051) contains a vulnerability in its playlist import functionality. When processing .m3u files, the application fails to properly validate the length of playlist entries, resulting in a buffer overflow condition. This flaw occurs during parsing of long URLs embedded in the playlist, allowing overwrite of Structured Exception Handler (SEH) records. The vulnerability is triggered upon opening a crafted playlist file and affects the Unicode parsing logic in the Windows client.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

BS.Player 2.57 (build 1051) contains a stack-based buffer overflow in its playlist import parser. When processing .m3u files, the application fails to validate the length of URL entries before copying them into a fixed-size buffer. This allows an attacker to overflow the buffer and overwrite Structured Exception Handler (SEH) records, enabling arbitrary code execution. The vulnerability affects Unicode string parsing during playlist processing.

MitigationUpgrade BS.Player to a version that includes the security fix for this vulnerability, or replace the affected software with an alternative media player that receives active security updates. Do not open untrusted .m3u playlist files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify BS.Player installation path and executable version
    Locate bsplayer.exe in the installation directory (commonly C:\Program Files\BS.Player or C:\Program Files (x86)\BS.Player). Right-click the executable, select Properties, and view the Version tab to obtain the File Version and Product Version.
    Affected if The product version displays 2.57 with build number 1051 exactly, indicating the vulnerable release.
  2. Confirm the specific build number
    In the same Version properties window, examine the 'Build' or 'Private Build' field if present. Alternatively, run 'bsplayer.exe -ver' from command line if supported, or check Help > About in the application interface.
    Affected if The build number matches 1051, confirming the exact vulnerable version.
  3. Check if playlist import functionality is accessible
    Launch BS.Player and navigate to the Playlist menu or File > Load Playlist option. Verify whether .m3u file import capability is present and operational.
    Affected if The playlist import feature is present and functional, enabling the vulnerable code path.
  4. Inspect .m3u file handling behavior
    Create or locate a test .m3u playlist file. Attempt to load it via the playlist import feature. Monitor for unexpected behavior, crashes, or error messages during the import process.
    Affected if The application crashes or exhibits abnormal behavior when loading .m3u files with long URL entries, confirming the vulnerability is triggerable.

You are affected if BS.Player version 2.57 build 1051 is installed and the playlist import feature is used to load .m3u files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade BS.Player to a version that includes the security fix for this vulnerability, or replace the affected software with an alternative media player that receives active security updates. Do not open untrusted .m3u playlist files.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-10016 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-10016 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data