dbcve.org
LibavApplication

CVE-2012-2777

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 decode_pic function in libavcodec/cavsdec.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, related to "width/height changing in CAVS," a different vulnerability than CVE-2012-2784.

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 the CAVS (Chinese AVS) video decoder's decode_pic function in libavcodec/cavsdec.c. The vulnerability involves improper handling of width/height parameters, likely allowing a specially crafted video file to trigger buffer overflows during frame dimension processing.

MitigationUpgrade FFmpeg to version 0.11 or later, or Libav to version 0.7.7/0.8.4 or later. Audit all deployments and systems that process CAVS video content.

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 if Libav or FFmpeg is installed
    Run 'ffmpeg -version' or 'avconv -version' to see which library is present and its executable name
    Affected if Either FFmpeg or Libav binaries are found on the system
  2. Check the installed version number
    Run 'ffmpeg -version' or 'avconv -version' and note the version string (e.g., 0.8, 0.7.3, 0.10.4, 0.4.6)
    Affected if The version falls within the affected ranges: Libav 0.7 through 0.8.3, or FFmpeg 0.3.x, 0.4.x, or <= 0.10.4
  3. Verify CAVS video decoding capability is available
    Run 'ffmpeg -codecs' or 'avconv -codecs' and search for 'cavs' or 'avs' in the output under video codecs
    Affected if The CAVS decoder (cavs) is listed as available (decoders are marked with 'D')
  4. Check if CAVS video files are being processed
    Search for .avs, .cavs, or other AVS format video files on the system, or check application logs that handle video processing
    Affected if CAVS video files exist or are being decoded by the affected library

The system is affected if FFmpeg/Libav version is within the vulnerable ranges AND the CAVS decoder is available or being used to process video content.

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, or Libav to version 0.7.7/0.8.4 or later. Audit all deployments and systems that process CAVS video content.

Recommended fix High confidence

FFmpeg 0.11 or later; Libav 0.7.7 or later (0.7.x branch); Libav 0.8.4 or later (0.8.x branch)

  1. Identify the current version of FFmpeg or Libav installed in your system
  2. For FFmpeg users: Upgrade to version 0.11 or any later release (e.g., 0.11.1, 0.11.2, etc.)
  3. For Libav 0.7.x users: Upgrade to version 0.7.7 or later
  4. For Libav 0.8.x users: Upgrade to version 0.8.4 or later
  5. Recompile and redeploy the updated library/application
  6. Verify the upgrade was successful by checking the version number (ffmpeg -version or avconv -version)
Caveat Major version upgrades may include API changes; review release notes and test thoroughly before production deployment

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,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 $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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