dbcve.org
LibvpxApplication · Webmproject

CVE-2012-0823

MEDIUM · 5.0 CVSS v2.0 Published 2012-02-23
Fix available
A fix is available. Upgrade to after 0.9.7 or later.
See remediation →
59/100
Remediation priority · Elevated
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
VP8 Codec SDK (libvpx) before 1.0.0 "Duclair" allows remote attackers to cause a denial of service (application crash) via (1) unspecified "corrupt input" or (2) by "starting decoding from a P-frame," which triggers an out-of-bounds read, related to "the clamping of motion vectors in SPLITMV blocks".

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

The VP8 Codec SDK (libvpx) before version 1.0.0 contains an out-of-bounds read vulnerability in the motion vector clamping logic for SPLITMV blocks. Attackers can trigger this by providing corrupt input or by initiating decode from a P-frame, causing a denial of service through application crash.

MitigationUpgrade libvpx to version 1.0.0 or later. Until the upgrade is applied, avoid processing untrusted VP8 video streams.

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
LibvpxApplication
Affected:<= 0.9.7= 0.9.0= 0.9.1= 0.9.2= 0.9.5= 0.9.6= 0.9.7

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
None
Integrity
None
Availability
Partial

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

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 libvpx version
    Run 'vpxdec --version' or 'vpxenc --version' if the command-line tools are installed, or check the library file with 'dpkg -l | grep libvpx' (Debian) or 'rpm -qa | grep libvpx' (RHEL), or inspect the shared library with 'ls -l /usr/lib/libvpx*'
    Affected if The version displayed is 0.9.0, 0.9.1, 0.9.2, 0.9.5, 0.9.6, or 0.9.7, or any version number lower than 1.0.0
  2. Identify applications using libvpx for VP8 decoding
    Search process memory or examine linked binaries with 'ldd <binary> | grep vpx' or check for usage of libvpx in running processes
    Affected if Any application linked against libvpx and configured to decode VP8 video streams is present
  3. Determine if processing of VP8 streams is occurring
    Monitor network traffic or file inputs for .webm, .ivf, or other VP8 container formats, or check application logs for VP8 decode activity
    Affected if The environment is actively decoding VP8 video from untrusted sources or P-frames

You are affected if libvpx version 0.9.7 or earlier is installed AND your system or applications decode VP8 video streams, especially from untrusted sources or P-frames.

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
Upgrade available Upgrade to a release after 0.9.7
Interim mitigation

Upgrade libvpx to version 1.0.0 or later. Until the upgrade is applied, avoid processing untrusted VP8 video streams.

Fix this in Libvpx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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