dbcve.org
FfmpegApplication

CVE-2014-125017

HIGH · 7.8 CVSS v3.1 Published 2022-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
A vulnerability classified as critical was found in FFmpeg 2.0. This vulnerability affects the function rpza_decode_stream. The manipulation leads to memory corruption. The attack can be initiated remotely. The name of the patch is Fixes Invalid Writes. 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 confidence

A memory corruption vulnerability in FFmpeg 2.0's rpza_decode_stream function allows remote attackers to cause invalid memory writes via crafted RPZA video files, leading to potential code execution or denial of service.

MitigationApply the vendor patch that fixes invalid writes in the rpza_decode_stream function, or update to a patched version of FFmpeg beyond 2.0.

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
FfmpegApplication
Affected:= 2.0

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FFmpeg version
    Run 'ffmpeg -version' or 'ffmpeg -buildconf' to display the version number and build information
    Affected if The version displayed is exactly 2.0
  2. Confirm RPZA decoder is present
    Run 'ffmpeg -decoders' and search for 'rpza' in the output, or run 'ffmpeg -h decoder=rpza'
    Affected if The RPZA decoder is listed as available in the decoder list
  3. Check build configuration for RPZA support
    Run 'ffmpeg -configuration' or 'ffmpeg -buildconf' and verify if RPZA is explicitly enabled in the build flags
    Affected if RPZA support is compiled into the binary and the version is 2.0

You are affected if FFmpeg version is exactly 2.0 and the RPZA decoder is available in your build.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch that fixes invalid writes in the rpza_decode_stream function, or update to a patched version of FFmpeg beyond 2.0.

Recommended fix Moderate confidence

Latest stable FFmpeg release (4.x or 5.x series, as FFmpeg 2.0 is from 2012)

  1. 1. Back up any existing FFmpeg 2.0 installations and configuration files.
  2. 2. Download the latest stable FFmpeg release from the official website (ffmpeg.org) or your distribution's package repository.
  3. 3. For source compilation: Clone the latest FFmpeg repository from git.videolan.org or download the current stable release tarball.
  4. 4. Compile and install the new version following standard build procedures, or install via package manager (e.g., apt-get install ffmpeg, yum install ffmpeg, brew install ffmpeg).
  5. 5. Verify the installation by running 'ffmpeg -version' to confirm the new version is active.
  6. 6. Test any critical video processing workflows to ensure functionality is intact.
Caveat Major version upgrades may introduce API changes; legacy encoding/decoding options or custom build configurations may need adjustment. Test thoroughly before production deployment.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-125017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-125017 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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