dbcve.org
ChromeWeb browser · Google

CVE-2013-0894

HIGH · 7.5 CVSS v2.0 Published 2013-02-23
Fix available
A fix is available. Upgrade to 25.0.1364.97 / 25.0.1364.99 or later.
See remediation →
84/100
Remediation priority · High
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
Buffer overflow in the vorbis_parse_setup_hdr_floors function in the Vorbis decoder in vorbisdec.c in libavcodec in FFmpeg through 1.1.3, as used in Google Chrome before 25.0.1364.97 on Windows and Linux and before 25.0.1364.99 on Mac OS X and other products, allows remote attackers to cause a denial of service (divide-by-zero error or out-of-bounds array access) or possibly have unspecified other impact via vectors involving a zero value for a bark map size.

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

Buffer overflow in FFmpeg's Vorbis decoder (vorbisdec.c) in the vorbis_parse_setup_hdr_floors function where a zero value for bark map size triggers divide-by-zero errors or out-of-bounds array access, potentially allowing remote code execution via malicious Vorbis audio files.

MitigationUpgrade FFmpeg to version 1.1.4 or later; ensure Google Chrome is updated to 25.0.1364.97+ (Windows/Linux) or 25.0.1364.99+ (Mac OS X). Apply input validation for bark map size values in vorbis_parse_setup_hdr_floors before array access calculations.

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
ChromeWeb browser
Affected:< 25.0.1364.99< 25.0.1364.97
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10
FfmpegApplication
Affected:<= 1.1.3
OpensuseOperating system
Affected:= 12.1= 12.2

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

AV:N/AC:L/Au:N/C:P/I:P/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 FFmpeg version
    Run 'ffmpeg -version' or 'ffmpeg -i' to display version information
    Affected if FFmpeg version is 1.1.3 or earlier (the affected range is <= 1.1.3)
  2. Check Google Chrome version
    Open Chrome, go to chrome://settings/help, or run 'google-chrome --version' from command line
    Affected if Chrome version is below 25.0.1364.97 (Windows/Linux) or below 25.0.1364.99 (Mac OS X)
  3. Verify Vorbis decoding capability is present
    Run 'ffmpeg -codecs | grep -i vorbis' or 'ffprobe -codecs 2>/dev/null | grep -i vorbis' to list enabled Vorbis decoders
    Affected if Vorbis decoder (libvorbis or native vorbis) appears in the codec list, indicating the vulnerable code path could be triggered
  4. Check Ubuntu distribution version if using system FFmpeg
    Run 'lsb_release -a' or check /etc/lsb-release for Ubuntu versions 12.04 or 12.10
    Affected if System is Ubuntu 12.04 or 12.10 and uses the system-packaged FFmpeg (these versions ship vulnerable FFmpeg versions)
  5. Check OpenSUSE if using system FFmpeg
    Run 'zypper info ffmpeg' or 'rpm -q ffmpeg' on OpenSUSE 12.1 or 12.2
    Affected if System is OpenSUSE 12.1 or 12.2 and has FFmpeg installed from official repositories

You are affected if you run FFmpeg version 1.1.3 or earlier, Chrome versions below 25.0.1364.97/99, or Ubuntu 12.04/12.10/OpenSUSE 12.1/12.2 with their default FFmpeg packages, and process untrusted Vorbis audio files with the Vorbis decoder enabled.

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 25.0.1364.97 / 25.0.1364.99 or later
Fixed in 25.0.1364.9725.0.1364.99
Interim mitigation

Upgrade FFmpeg to version 1.1.4 or later; ensure Google Chrome is updated to 25.0.1364.97+ (Windows/Linux) or 25.0.1364.99+ (Mac OS X). Apply input validation for bark map size values in vorbis_parse_setup_hdr_floors before array access calculations.

Fix this in Chrome 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-2013-0894 — 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-2013-0894 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