CVE-2014-125013
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 and classified as problematic. This issue affects the function msrle_decode_frame of the file libavcodec/msrle.c. The manipulation leads to memory corruption. The attack may 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 · moderate confidenceMemory corruption vulnerability in FFmpeg 2.0's MSRLE video codec decoder. The msrle_decode_frame function in libavcodec/msrle.c contains improper memory handling during processing of MSRLE-encoded video frames, allowing corruption of memory contents.
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 versionRun 'ffmpeg -version' or check the installed package version to determine if it is exactly version 2.0Affected if The installed FFmpeg version is exactly 2.0
-
Locate the MSRLE decoder moduleCheck for the presence of libavcodec/msrle.c or the compiled MSRLE decoder library (msrle.so, msrle.dll, or similar) in the FFmpeg installation directoryAffected if The MSRLE decoder component exists in the FFmpeg installation
-
Verify MSRLE codec availabilityRun 'ffmpeg -codecs | grep -i msrle' to list whether the MSRLE decoder is compiled and available in the buildAffected if The MSRLE decoder is listed as available in ffmpeg -codecs output
-
Identify MSRLE-encoded video files in useScan log files, recent media files, or application usage logs for files with .msrle extension or MSRLE-encoded content being processedAffected if MSRLE-encoded video files are being processed or have been processed by the FFmpeg instance
A user is affected if they are running FFmpeg version 2.0 and using it to process MSRLE-encoded video files, as the memory corruption vulnerability exists specifically in the msrle_decode_frame function during MSRLE decoding.
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 patch to fix the memory corruption in msrle_decode_frame. Until patched, avoid processing untrusted MSRLE-encoded video files with affected FFmpeg versions.
FFmpeg 6.x or later stable release (e.g., FFmpeg 6.1, 7.x)
- 1. Back up any existing FFmpeg installations and configuration files
- 2. Download the latest stable FFmpeg release from ffmpeg.org (such as FFmpeg 6.x or newer)
- 3. Remove the existing FFmpeg 2.0 installation completely
- 4. Compile and install the new version from source, or install via package manager
- 5. Verify the installation by running 'ffmpeg -version'
- 6. Test any dependent applications to ensure they function correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-125013 — 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-125013 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