FedoraOperating system · Fedoraproject
CVE-2019-9133
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 · uneditedWhen processing subtitles format media file, KMPlayer version 2018.12.24.14 or lower doesn't check object size correctly, which leads to integer underflow then to memory out-of-bound read/write. An attacker can exploit this issue by enticing an unsuspecting user to open a malicious 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 · moderate confidenceKMPlayer fails to validate object size when parsing subtitle format media files, which causes an integer underflow. This leads to out-of-bounds memory read/write. An attacker exploits this by tricking a user into opening a malicious subtitle file.
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
FedoraOperating system
= 29= 30<= 2018.12.24.14CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify KMPlayer is installedCheck if KMPlayer application exists on the system. On Linux/Fedora, look for kmplayer in package manager (dnf list installed kmplayer) or check for the binary at /usr/bin/kmplayer or /usr/local/bin/kmplayerAffected if KMPlayer is not installed on the system
-
Determine installed KMPlayer versionRun kmplayer --version or check package version via dnf info kmplayer. Note the exact version number installedAffected if Version is <= 2018.12.24.14 or version cannot be determined (older package)
-
Confirm host operating system versionCheck Fedora version with 'cat /etc/fedora-release' or 'hostnamectl'Affected if Running Fedora 29 or Fedora 30
-
Verify subtitle parsing functionalityKMPlayer parses subtitle files as a core feature when loading media. Confirm the application can load subtitle files (.srt, .ass, .ssa, .sub formats) - this is enabled by default when the player is functionalAffected if KMPlayer can parse subtitle files (this is the default behavior when KMPlayer is running)
-
Check for recent subtitle file activityReview recent files opened in KMPlayer or check browser/download folders for recently downloaded subtitle files from untrusted sources using 'find /home -name "*.srt" -mtime -7' or similarAffected if User has opened or attempted to open subtitle files from untrusted or unknown sources
User is affected if KMPlayer version <= 2018.12.24.14 is installed on Fedora 29 or 30, or if an older KMPlayer version is running and parsing subtitle files.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade KMPlayer to a version higher than 2018.12.24.14, and avoid opening subtitle files from untrusted sources.
Fix this in Fedora
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-9133 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-9133 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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