ChromeWeb browser · Google
CVE-2013-0890
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 · uneditedMultiple unspecified vulnerabilities in the IPC layer in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, allow remote attackers to cause a denial of service (memory corruption) or possibly have other impact via unknown vectors.
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 confidenceMultiple vulnerabilities in the Inter-Process Communication (IPC) layer of Google Chrome allow remote attackers to cause memory corruption, leading to denial of service or potentially arbitrary code execution. The vulnerabilities exist in versions prior to 25.0.1364.97 on Windows/Linux and 25.0.1364.99 on Mac OS X.
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 Google Chrome version on Windows or LinuxOpen Chrome and navigate to chrome://version, or click the menu icon > Help > About Google Chrome. Record the version number shown.Affected if The displayed version is below 25.0.1364.97 (for example, 25.0.1364.0, 24.0.1312.56, etc.)
-
Check Google Chrome version on Mac OS XOpen Chrome, click Chrome menu > About Google Chrome. Record the version number shown.Affected if The displayed version is below 25.0.1364.99 (for example, 25.0.1364.0, 24.0.1312.56, etc.)
-
Check openSUSE version if Chrome is installed from distribution packagesOpen a terminal and run: cat /etc/os-release or lsb_release -a. Look for the VERSION line indicating 12.1 or 12.2.Affected if The system runs openSUSE 12.1 or 12.2 and has Google Chrome installed from that distribution's repositories.
A user is affected if they run Google Chrome version 25.0.1364.96 or earlier on Windows/Linux, version 25.0.1364.98 or earlier on Mac OS X, or openSUSE 12.1/12.2 with a vulnerable Chrome package installed.
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 (Windows/Linux) or version 25.0.1364.99 or later (Mac OS X). In enterprise environments, deploy the update via centralized software distribution mechanisms and verify completion across all affected endpoints.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0890 — 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-0890 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