dbcve.org
FfmpegApplication

CVE-2014-125025

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 classified as problematic has been found in FFmpeg 2.0. This affects the function decode_pulses. The manipulation leads to memory corruption. It is possible to initiate 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 confidence

Memory corruption vulnerability in FFmpeg 2.0's decode_pulses function allows remote attackers to potentially execute arbitrary code or cause a denial of service via crafted media files.

MitigationApply the vendor patch or upgrade to a patched version of FFmpeg to remediate the memory corruption issue in the decode_pulses function.

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 if FFmpeg is installed
    Run `ffmpeg -version` or `ffmpeg -buildconf` to display version information
    Affected if FFmpeg is not installed or command fails - not affected
  2. Verify installed FFmpeg version
    Parse the output from `ffmpeg -version` to confirm the exact version number is 2.0
    Affected if Version shown is exactly 2.0 (e.g., 'ffmpeg version 2.0' or 'ffmpeg 2.0') - proceed to next check
  3. Confirm libavcodec component is present
    Run `ffmpeg -codecs` or `ffmpeg -formats` to list supported codecs and verify libavcodec is available
    Affected if libavcodec is present - the decode_pulses function exists in this library for ATRAC3 audio decoding
  4. Identify if ATRAC3 audio decoding is enabled
    Search the `ffmpeg -codecs` output for 'atrac3' or 'ATRAC3' in the codec list
    Affected if ATRAC3 decoder is listed and enabled, the decode_pulses function can be triggered by specially crafted ATRAC3 audio streams in media files

You are affected if FFmpeg version 2.0 is installed AND you process media files (especially those containing ATRAC3 audio) with this installation - the decode_pulses function will be invoked when decoding such 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch or upgrade to a patched version of FFmpeg to remediate the memory corruption issue in the decode_pulses function.

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-125025 — 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-125025 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