CVE-2014-125002
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 was found in FFmpeg 2.0. It has been classified as problematic. Affected is the function dnxhd_init_rc of the file libavcodec/dnxhdenc.c. The manipulation leads to memory corruption. It is possible to launch 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 the dnxhd_init_rc function of libavcodec/dnxhdenc.c in FFmpeg 2.0. The issue allows memory corruption during DNxHD encoding operations, potentially exploitable remotely via crafted media 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.
-
Identify installed FFmpeg versionRun 'ffmpeg -version' or 'avconv -version' to display the version numberAffected if The version shown is exactly 2.0 (2.0.x variants may also be affected)
-
Confirm DNxHD encoder availabilityRun 'ffmpeg -encoders 2>/dev/null | grep -i dnx' or check encoder list output for 'dnxhd' or 'dnxhd_encoder' entryAffected if The DNxHD encoder is listed as available in the build
-
Check for DNxHD encoding usageInspect application logs, media processing scripts, or command history for DNxHD encoding operations (typically invoked with '-c:v dnxhd' or '-vcodec dnxhd' in ffmpeg commands)Affected if DNxHD encoding is actively being performed on media files
-
Verify affected binary/libraryCheck the libavcodec library file (libavcodec.so* or avcodec.dll) and its version, or run 'ffmpeg -buildinfo' if available to see compiled componentsAffected if The binary links to FFmpeg 2.0 libraries and includes the vulnerable dnxhdenc.c module
You are affected if FFmpeg version 2.0 is installed and DNxHD encoding operations are performed using the vulnerable dnxhd_init_rc function in libavcodec/dnxhdenc.c.
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 official FFmpeg patch for this vulnerability. If no patch available, upgrade FFmpeg to a version beyond 2.0 that contains the fix. Input validation and bounds checking in the affected function are required.
FFmpeg 2.3 or later stable release (e.g., FFmpeg 2.8 'Fabian' or newer)
- 1. Obtain a newer version of FFmpeg from the official source (ffmpeg.org/download.html or git.videolan.org)
- 2. Verify the current installed version: ffmpeg -version
- 3. Compile and install the new version, or install via package manager if a fixed version is available
- 4. Verify the fix is applied by checking the dnxhdenc.c file in the new version contains the corrected dnxhd_init_rc function
- 5. Test that DNxHD encoding functionality works correctly with the new build
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-125002 — 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-125002 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