CVE-2014-125007
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 classified as problematic was found in FFmpeg 2.0. Affected by this vulnerability is the function intra_pred of the file libavcodec/hevcpred_template.c. The manipulation leads to memory corruption. The attack can be launched 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 confidenceA memory corruption vulnerability exists in FFmpeg 2.0 within the intra_pred function of libavcodec/hevcpred_template.c, which handles HEVC/H.265 video decoding intra-prediction. The flaw allows memory corruption, likely through improper bounds checking or buffer handling during prediction operations. A remote attacker could exploit this by tricking a user into processing a specially crafted HEVC video 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= 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 FFmpeg installation and versionRun 'ffmpeg -version' to display the installed FFmpeg versionAffected if Version displayed is exactly 2.0
-
Check for HEVC/H.265 decoding supportRun 'ffmpeg -codecs 2>/dev/null | grep -i hevc' or 'ffmpeg -decoders 2>/dev/null | grep -i hevc' to list HEVC decodersAffected if HEVC decoder (hevc or libx265) is listed as available
-
Verify hevcpred_template.c is present in the FFmpeg buildLocate the libavcodec directory (e.g., 'ffmpeg -v 2>&1 | grep libavcodec' shows path) and check for hevcpred_template.c fileAffected if The file exists in the FFmpeg installation's source or libraries
-
Confirm HEVC file processing capabilityAttempt to decode a valid HEVC/H.265 test file using 'ffmpeg -i input_hevc.mkv -f null - 2>&1' to verify the decoder is functionalAffected if HEVC decoding runs without error, confirming the vulnerable code path is present
Affected if FFmpeg version is exactly 2.0 and HEVC/H.265 decoding support is enabled in the build, allowing the intra_pred function in hevcpred_template.c to be invoked.
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 to fix the intra_pred function memory corruption. Update to a patched version of FFmpeg 2.0 or later, and validate that HEVC decoding handles malformed streams without memory corruption.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-125007 — 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-125007 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