dbcve.org
LibavApplication

CVE-2012-2800

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
Unspecified vulnerability in the ff_ivi_process_empty_tile function in libavcodec/ivi_common.c in FFmpeg before 0.11, and Libav 0.7.x before 0.7.7 and 0.8.x before 0.8.4, has unknown impact and attack vectors in which the "tile size ... mismatches parameters" and triggers "writing into a too small array."

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 · high confidence

A buffer overflow vulnerability in the ff_ivi_process_empty_tile function in libavcodec/ivi_common.c allows writing beyond array bounds when processing AVI files with tile size parameters that mismatch the declared dimensions in the Indeo video decoder.

MitigationUpgrade to FFmpeg 0.11+, Libav 0.7.7+, or Libav 0.8.4+ to patch the vulnerable code. Avoid processing untrusted AVI files with the Indeo codec until patched.

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
LibavApplication
Affected:= 0.8= 0.8.1= 0.8.2= 0.8.3= 0.7= 0.7.1= 0.7.2= 0.7.3= 0.7.4= 0.7.5= 0.7.6
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 installed library
    Run 'ffmpeg -version' or 'avconv -version' to determine if FFmpeg or Libav is installed and note the binary name used.
    Affected if Either ffmpeg or libav is installed with the binary named ffmpeg or avconv respectively.
  2. Determine version number
    Parse the version output from the previous step. For ffmpeg, look for versions like 0.3.x, 0.4.x, 0.10.x or earlier. For libav/avconv, look for versions 0.7.x through 0.8.3.
    Affected if The version is Libav 0.7.x, 0.8, 0.8.1, 0.8.2, or 0.8.3; or FFmpeg 0.3.x, 0.4.x, 0.4.2 through 0.4.6, or 0.10.4 and earlier.
  3. Check if Indeo decoder is available
    Run 'ffmpeg -codecs 2>/dev/null | grep -i indeo' or 'avconv -codecs 2>/dev/null | grep -i indeo' to list decoders and look for indeo3, indeo4, or indeo5.
    Affected if An Indeo decoder (indeo3, indeo4, or indeo5) is listed as supported.
  4. Verify AVI demuxer is available
    Run 'ffmpeg -formats 2>/dev/null | grep -i avi' or 'avconv -formats 2>/dev/null | grep -i avi' to confirm AVI format demuxing is enabled.
    Affected if AVI format is listed as a supported format (DEMUX in the output).

You are affected if you have FFmpeg 0.10.4 or earlier, or FFmpeg 0.3.x/0.4.x, or Libav 0.7.x through 0.8.3 installed AND the Indeo video decoder is available for processing AVI 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
Upgrade available Upgrade to a release after 0.10.4
Interim mitigation

Upgrade to FFmpeg 0.11+, Libav 0.7.7+, or Libav 0.8.4+ to patch the vulnerable code. Avoid processing untrusted AVI files with the Indeo codec until patched.

Recommended fix High confidence

FFmpeg 0.11 or later; or Libav 0.7.7+/0.8.4+

  1. Check the current version of FFmpeg or Libav installed (e.g., run 'ffmpeg -version' or 'avconv -version')
  2. Back up any custom configurations or scripts that rely on the current FFmpeg/Libav version
  3. Upgrade FFmpeg to version 0.11 or later (e.g., install FFmpeg 0.11, 0.11.1, or newer stable release)
  4. OR if using Libav: upgrade to version 0.7.7 or later, or 0.8.4 or later
  5. Verify the new version is installed correctly by running 'ffmpeg -version' or 'avconv -version'
  6. Test critical video processing workflows to ensure functionality is preserved
Caveat Upgrading major versions may introduce API changes or deprecate certain encoding/decoding options; test custom integrations thoroughly

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

Fix this in Libav Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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