dbcve.org
KmplayerApplication · Pandora

CVE-2018-5200

HIGH · 7.8 CVSS v3.1 Published 2018-12-20
Fix available
A fix is available. Upgrade to after 4.2.2.15 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
KMPlayer 4.2.2.15 and earlier have a Heap Based Buffer Overflow Vulnerability. It could be exploited with a crafted FLV format file. The problem is that more frame data is copied to heap memory than the size specified in the frame header. This results in a memory corruption and remote code execution.

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

Heap-based buffer overflow in KMPlayer 4.2.2.15 and earlier when parsing FLV files. The vulnerability occurs when the player copies more frame data to heap memory than the size specified in the frame header, causing memory corruption that can lead to remote code execution.

MitigationAvoid opening untrusted or unverified FLV files with vulnerable KMPlayer versions. Update to a patched version if available, or migrate to an alternative media player until a fix is released.

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
KmplayerApplication
Affected:<= 4.2.2.15

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. Verify KMPlayer is installed
    Locate KMPlayer on the system - check common installation directories such as C:\Program Files\KMPlayer or C:\Program Files (x86)\KMPlayer, or search for kmplayer.exe in the system
    Affected if KMPlayer executable is found on the system
  2. Identify installed KMPlayer version
    Right-click the kmplayer.exe file, select Properties, then navigate to the Details tab to view the File Version information
    Affected if The displayed version is 4.2.2.15 or earlier (any version number lower than or equal to 4.2.2.15)
  3. Confirm FLV playback capability exists
    Check if the KMPlayer installation includes FLV support by verifying the presence of FLV-related codecs or checking the supported formats list within the player
    Affected if FLV file format support is present in the KMPlayer installation

The system is affected if KMPlayer is installed with a version numbered 4.2.2.15 or lower and the player supports FLV file playback.

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 a release after 4.2.2.15
Interim mitigation

Avoid opening untrusted or unverified FLV files with vulnerable KMPlayer versions. Update to a patched version if available, or migrate to an alternative media player until a fix is released.

Fix this in Kmplayer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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