CVE-2014-125004
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 · uneditedA vulnerability has been found in FFmpeg 2.0 and classified as problematic. This vulnerability affects the function decode_hextile of the file libavcodec/vmnc.c. The manipulation leads to memory corruption. The attack can be initiated remotely. It is recommended to apply a patch to fix this issue.
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 confidenceA memory corruption vulnerability exists in FFmpeg 2.0 within the decode_hextile function in libavcodec/vmnc.c. This function processes VMnc (VMware screen) codec data, and improper handling during hextile decoding leads to memory corruption that could potentially be exploited via specially crafted video files.
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= 2.0CVSS 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.
-
Check installed FFmpeg versionRun 'ffmpeg -version' and examine the version string in the outputAffected if The version displayed is exactly 2.0 (e.g., 'ffmpeg version 2.0' or 'ffmpeg 2.0')
-
Verify libavcodec presenceCheck for the presence of libavcodec shared library (typically libavcodec.so or libavcodec.dll in system paths)Affected if libavcodec exists and is linked to FFmpeg 2.0
-
Confirm vmnc codec availabilityRun 'ffmpeg -codecs | grep -i vmnc' or 'ffmpeg -encoders | grep -i vmnc' to list supported codecsAffected if The vmnc (VMware Screen) codec is listed as available in FFmpeg 2.0, indicating the vulnerable decode_hextile code path is present
-
Check for patched binary versionIf ffmpeg was rebuilt after the CVE disclosure, check for version suffixes or build dates using 'ffmpeg -version'Affected if The binary is the original 2.0 release with no subsequent build patches applied to fix the memory corruption in libavcodec/vmnc.c
A system is affected only if FFmpeg version 2.0 is installed with the vmnc codec enabled, as the memory corruption in decode_hextile requires both the vulnerable version and the VMnc decoding functionality to be present.
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.
dbcve · scopedApply the vendor-supplied patch for this specific vulnerability in FFmpeg 2.0, or upgrade to a patched version of FFmpeg that addresses the memory corruption issue in the decode_hextile function.
Latest stable FFmpeg release (e.g., 6.x or later)
- 1. Identify the current FFmpeg installation: ffmpeg -version
- 2. Download the latest stable FFmpeg release from ffmpeg.org/download.html or compile from source
- 3. Install the new version, ensuring all dependencies are also updated
- 4. Verify the installation: ffmpeg -version
- 5. Test that the vmnc decoder works with your use case
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-125004 — 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-2014-125004 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