dbcve.org
ChromeWeb browser · Google

CVE-2013-0881

MEDIUM · 5.0 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 →
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
Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, allows remote attackers to cause a denial of service (incorrect read operation) via crafted data in the Matroska container format.

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

Google Chrome versions prior to 25.0.1364.97 (Windows/Linux) and 25.0.1364.99 (Mac) contain an incorrect read vulnerability when parsing crafted Matroska (MKV) container files, leading to a denial of service condition.

MitigationUpdate Google Chrome to version 25.0.1364.97 or later (Windows/Linux) or 25.0.1364.99 or later (Mac).

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.97< 25.0.1364.99
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
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 Google Chrome version on Windows or Linux
    Navigate to chrome://settings/help or type 'About Google Chrome' in the address bar to display the version number
    Affected if Version displayed is lower than 25.0.1364.97 on Windows or Linux
  2. Check Google Chrome version on macOS
    Click the Chrome menu, select 'About Google Chrome' to display the version number
    Affected if Version displayed is lower than 25.0.1364.99 on Mac
  3. Check OpenSUSE package version
    Run 'rpm -qa | grep -i chrome' or 'zypper se google-chrome' to retrieve the installed Chrome package version
    Affected if OpenSUSE 12.1 or 12.2 has Google Chrome installed with a version lower than 25.0.1364.97
  4. Verify ability to process Matroska files
    Check if Chrome is configured to open .mkv files or if the user commonly opens such files in the browser
    Affected if Chrome is set to handle MKV files and an affected version is installed

You are affected if you are running Google Chrome on any platform with a version below 25.0.1364.97 (Windows/Linux), below 25.0.1364.99 (Mac), or on OpenSUSE 12.1/12.2 with an unpatched Chrome package.

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

Update Google Chrome to version 25.0.1364.97 or later (Windows/Linux) or 25.0.1364.99 or later (Mac).

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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