dbcve.org
FfmpegApplication

CVE-2014-125023

MEDIUM · 5.5 CVSS v3.1 Published 2022-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
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 was found in FFmpeg 2.0. It has been declared as problematic. Affected by this vulnerability is the function truemotion1_decode_header of the component Truemotion1 Handler. 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 confidence

A memory corruption vulnerability exists in FFmpeg 2.0's Truemotion1 video codec handler. The truemotion1_decode_header function fails to properly validate input data when processing TrueMotion video files, leading to memory corruption that could potentially be exploited for arbitrary code execution or denial of service.

MitigationUpdate FFmpeg to a patched version (2.0.1+ or later stable releases). If immediate patching is not possible, restrict processing of untrusted Truemotion1 video files and implement input validation at the application layer.

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
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 checks

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

  1. Check installed FFmpeg version
    Run 'ffmpeg -version' and note the version number in the output
    Affected if The version shown is exactly 2.0 (not 2.0.1 or later, not an earlier version)
  2. Identify FFmpeg binary location
    Run 'which ffmpeg' or 'where ffmpeg' to locate the executable
    Affected if FFmpeg binary exists and version is 2.0
  3. Check for Truemotion1 codec support
    Run 'ffmpeg -codecs 2>&1 | grep -i truemotion' or 'ffmpeg -formats 2>&1 | grep -i truemotion' to see if Truemotion1 is listed as an available decoder
    Affected if Truemotion1 decoder (codec ID 27 or 'truemotion1') appears as available and the FFmpeg version is 2.0
  4. Verify active processing of Truemotion video files
    Inspect any application logs, transcoding job records, or media processing pipelines that handle .avi, .mov, or raw Truemotion video files
    Affected if The system processes or has processed any TrueMotion1 video files using FFmpeg 2.0

A system is affected only if FFmpeg version is exactly 2.0 and it processes or has processed Truemotion1 video files.

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

Update FFmpeg to a patched version (2.0.1+ or later stable releases). If immediate patching is not possible, restrict processing of untrusted Truemotion1 video files and implement input validation at the application layer.

Recommended fix Moderate confidence

Current stable FFmpeg release (6.x or 7.x series)

  1. 1. Backup your current FFmpeg 2.0 installation and any configuration files.
  2. 2. Obtain a current stable release of FFmpeg from the official source (ffmpeg.org/download.html) or your distribution's package manager.
  3. 3. Uninstall FFmpeg 2.0 completely before installing the new version to avoid conflicts.
  4. 4. Install the latest stable FFmpeg release (such as the most recent 6.x or 7.x release).
  5. 5. Verify the installation was successful by running 'ffmpeg -version'.
  6. 6. Test your specific use case or workflow to ensure compatibility with the new version.
Caveat FFmpeg 2.0 is extremely old (2012). Upgrading to a modern release may introduce breaking changes in command-line options, API behavior, or library dependencies. Review the release notes for major versions between 2.0 and your target version.

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-125023 — 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-125023 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