dbcve.org
Mpc HcApplication

CVE-2013-3488

HIGH · 7.8 CVSS v3.1 Published 2020-01-31
Fix available
A fix is available. Upgrade to 1.7.0.7858 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Stack-based buffer overflow in Media Player Classic - Home Cinema (MPC-HC) before 1.7.0.7858 allows remote attackers to execute arbitrary code via a crafted MPEG-2 Transport Stream (M2TS) file.

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

A stack-based buffer overflow vulnerability exists in MPC-HC (Media Player Classic - Home Cinema) versions prior to 1.7.0.7858. The vulnerability is triggered when parsing specially crafted MPEG-2 Transport Stream (M2TS) files, allowing an attacker to overwrite stack memory and execute arbitrary code remotely.

MitigationUpdate MPC-HC to version 1.7.0.7858 or later. Avoid opening untrusted M2TS files from unknown sources until the update is applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mpc HcApplication
Affected:< 1.7.0.7858

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Check if MPC-HC is installed
    Look for MPC-HC in the system: check Program Files folder, or search for 'mpc-hc.exe' using file explorer or the 'where' command in Command Prompt (e.g., where mpc-hc.exe). Also check Add/Remove Programs for Media Player Classic - Home Cinema.
    Affected if MPC-HC is found on the system
  2. Determine the installed MPC-HC version
    Right-click the mpc-hc.exe file, select Properties, then go to the Details tab to view the File Version. Alternatively, open MPC-HC, go to Help > About and note the version number displayed.
    Affected if The version displayed is lower than 1.7.0.7858
  3. Verify M2TS file handling capability
    Check if MPC-HC has file associations or can open .m2ts files. Look for .m2ts in the file types registered with MPC-HC (in Windows, check Default Programs > Set Associations). Try opening any .m2ts file with MPC-HC if one is available.
    Affected if MPC-HC can open or has associations with M2TS files, indicating the vulnerable parsing feature is active

If MPC-HC is installed with a version lower than 1.7.0.7858 and can handle M2TS files, the environment is affected by this vulnerability.

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
Upgrade available Upgrade to 1.7.0.7858 or later
Fixed in 1.7.0.7858
Interim mitigation

Update MPC-HC to version 1.7.0.7858 or later. Avoid opening untrusted M2TS files from unknown sources until the update is applied.

Fix this in Mpc Hc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3488 — 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-2013-3488 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