CVE-2014-125005
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, which was classified as problematic, was found in FFmpeg 2.0. This affects the function decode_vol_header of the file libavcodec/mpeg4videodec.c. The manipulation leads to memory corruption. It is possible to initiate the attack 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 · moderate confidenceMemory corruption vulnerability in FFmpeg 2.0's MPEG4 video decoder (mpeg4videodec.c) within the decode_vol_header function. The vulnerability allows manipulation to corrupt memory, potentially leading to arbitrary code execution or denial of service. Attack is remotely exploitable 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.
-
Verify FFmpeg is installedRun `ffmpeg -version` or `which ffmpeg` to confirm FFmpeg is present on the systemAffected if FFmpeg is not installed or not found in PATH, then this CVE does not apply
-
Confirm the installed version is 2.0Run `ffmpeg -version` and examine the output version string. Look for a version number of exactly 2.0 (e.g., ffmpeg version 2.0, ffmpeg-2.0, or 2.0.x)Affected if The installed version is exactly 2.0, then this CVE applies. If the version is earlier than 2.0, later than 2.0, or cannot be determined, this specific CVE does not apply (later versions may have fixed this, earlier versions may have different vulnerabilities)
-
Check if MPEG4 video decoding capability is availableRun `ffmpeg -codecs 2>/dev/null | grep -i mpeg4` to list available MPEG4 video decoders, or attempt to decode a test MPEG4 file with `ffmpeg -i test.mp4 -f null -`Affected if MPEG4 video decoding is available and the version is 2.0, then the vulnerable decode_vol_header function in mpeg4videodec.c is present and could be triggered by processing a specially crafted MPEG4 video file
You are affected by this CVE if FFmpeg version 2.0 is installed AND MPEG4 video decoding capability is present on the system and you process video files with it.
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 dataApply the official FFmpeg patch for this vulnerability. In the meantime, validate and sanitize input from untrusted video sources before processing with FFmpeg, and consider using updated versions of FFmpeg that contain the fix.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-125005 — 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-125005 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