dbcve.org
FfmpegApplication

CVE-2012-2795

HIGH · 10.0 CVSS v2.0 Published 2012-09-10
Fix available
A fix is available. Upgrade to after 0.10.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Multiple unspecified vulnerabilities in libavcodec/wmalosslessdec.c in FFmpeg before 0.11 have unknown impact and attack vectors related to (1) size of "mclms arrays," (2) "a get_bits(0) in decode_ac_filter," and (3) "too many bits in decode_channel_residues()."

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

Multiple heap-based vulnerabilities exist in libavcodec/wmalosslessdec.c in FFmpeg versions before 0.11, specifically in WMA Lossless audio decoding. The issues include improper bounds checking on mclms array sizes, an invalid get_bits(0) call in decode_ac_filter, and excessive bit consumption in decode_channel_residues(). These can likely cause heap corruption leading to code execution or denial of service.

MitigationUpgrade FFmpeg to version 0.11 or later. If upgrading is not immediately feasible, apply vendor patches for this CVE or disable WMA Lossless audio decoding in affected deployments.

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:<= 0.10.4= 0.3= 0.3.1= 0.3.2= 0.3.3= 0.3.4= 0.4.0= 0.4.2= 0.4.3= 0.4.4= 0.4.5= 0.4.6

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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 installation
    Run `ffmpeg -version` to see the installed FFmpeg version. If not installed, run `which ffmpeg` or check common paths like /usr/bin/ffmpeg.
    Affected if FFmpeg is not installed, the check does not apply.
  2. Determine exact FFmpeg version
    Parse the output from `ffmpeg -version` which typically shows version in the format 'ffmpeg version X.Y.Z' or similar. Compare this version number against the affected range: versions 0.3.0 through 0.4.6, and any version 0.10.4 or lower.
    Affected if The installed version is 0.3, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.4.0, 0.4.2, 0.4.3, 0.4.4, 0.4.5, 0.4.6, or any version 0.10.4 or below.
  3. Check if WMA Lossless decoder is available
    Run `ffmpeg -codecs 2>/dev/null | grep -i wmalossless` or `ffmpeg -decoders 2>/dev/null | grep -i wmalossless` to see if the WMA Lossless audio decoder is compiled into the build.
    Affected if The WMA Lossless decoder is present and available in the build.
  4. Verify the vulnerable library file exists
    Locate the libavcodec library file (such as libavcodec.so or libavcodec.dll) and check its version if possible. On Linux: `ls -l /usr/lib/libavcodec.so*` or `ldd $(which ffmpeg)` to see linked libraries.
    Affected if The libavcodec library linked to FFmpeg is from an affected version.

You are affected if you have any FFmpeg version from 0.3.0 through 0.4.6 or version 0.10.4 or lower that includes the WMA Lossless decoder in its 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
Upgrade available Upgrade to a release after 0.10.4
Interim mitigation

Upgrade FFmpeg to version 0.11 or later. If upgrading is not immediately feasible, apply vendor patches for this CVE or disable WMA Lossless audio decoding in affected deployments.

Recommended fix High confidence

FFmpeg 0.11 or later (current stable release recommended: 7.1)

  1. 1. Check current FFmpeg version using 'ffmpeg -version'
  2. 2. Download FFmpeg 0.11 or later from the official website (ffmpeg.org) or your distribution's package manager
  3. 3. Install the updated FFmpeg version following your platform's standard installation procedures
  4. 4. Verify the installation was successful by running 'ffmpeg -version' and confirming the version number is 0.11 or higher
  5. 5. Test that any applications or scripts relying on FFmpeg continue to function correctly after the upgrade
Caveat Major version upgrades in FFmpeg may include API/ABI changes that could require recompilation of dependent software or updates to integration code

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

Fix this in Ffmpeg Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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