ChromeWeb browser · Google
CVE-2013-0891
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 · uneditedInteger overflow in 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 or possibly have unspecified other impact via a blob.
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 confidenceInteger overflow vulnerability in Google Chrome's blob handling code affecting versions before 25.0.1364.97 (Windows/Linux) and 25.0.1364.99 (Mac). The overflow occurs when processing malformed blob objects, potentially allowing remote attackers to cause denial of service or achieve unspecified impact via specially crafted web 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
ChromeWeb browser
< 25.0.1364.97< 25.0.1364.99= 12.1= 12.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Chrome version on Windows or LinuxOpen Chrome and navigate to chrome://version, or click Menu > Help > About Google Chrome. Alternatively, check the application's properties file or use the command line: chrome --versionAffected if The displayed version is earlier than 25.0.1364.97 on Windows or Linux
-
Check Chrome version on Mac OS XOpen Chrome and click Chrome menu > About Google Chrome, or check the application bundle infoAffected if The displayed version is earlier than 25.0.1364.99 on Mac OS X
-
Check installed Chrome package on OpenSUSEOn OpenSUSE 12.1 or 12.2, run: rpm -qa | grep -i chrome or zypper search -i google-chrome to list installed Chrome packagesAffected if OpenSUSE version is 12.1 or 12.2 and Google Chrome is installed from the default repositories
You are affected if Chrome version is below 25.0.1364.97 on Windows/Linux, below 25.0.1364.99 on Mac OS X, or if you are running Chrome on OpenSUSE 12.1 or 12.2 with a vulnerable Chrome package.
Generated from the published advisory. Verify against your own configuration.
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 data25.0.1364.9725.0.1364.99
Update Google Chrome to version 25.0.1364.97 or later on Windows/Linux, or 25.0.1364.99 or later on Mac OS X. In enterprise environments, test the browser update in a controlled environment before broad deployment to ensure compatibility with internal applications.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0891 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0891 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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