ChromeWeb browser · Google
CVE-2013-0900
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 · uneditedRace condition in the International Components for Unicode (ICU) functionality 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 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 confidenceRace condition in Google Chrome's bundled International Components for Unicode (ICU) library allows remote attackers to cause denial of service or potentially execute unspecified code via unknown vectors. The vulnerability exists in Chrome versions prior to 25.0.1364.97 (Windows/Linux) and 25.0.1364.99 (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
Debian LinuxOperating system
= 6.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 installed Google Chrome versionOpen Chrome, click the menu icon (three dots), select Help > About Google Chrome. Alternatively, navigate to chrome://settings/help or run 'google-chrome --version' from command line.Affected if Version is below 25.0.1364.97 on Windows/Linux or below 25.0.1364.99 on Mac OS X
-
Identify if custom application uses bundled ICU librarySearch for ICU library files (icu*.dll on Windows, libicu*.so on Linux, libicu*.dylib on Mac) in the application's installation directory or bundled resources folder.Affected if Application bundles an ICU library version prior to the patched release (verify against ICU version release notes around early 2013)
-
Check system ICU package version on Debian 6.0Run 'dpkg -l | grep icu' or 'apt-cache policy libicu48' (or relevant ICU package name) to list installed ICU packages.Affected if ICU library package version matches the vulnerable version shipped with Debian 6.0
-
Verify Chrome process is using vulnerable ICU codeIf Chrome is running, inspect loaded modules (task manager in Chrome, or Process Explorer on Windows, lsof on Linux) to confirm ICU library is loaded. The vulnerability triggers when ICU handles certain Unicode data.Affected if Chrome is actively using an ICU library from a version known to contain the race condition vulnerability
A user is affected if they are running any Google Chrome version below 25.0.1364.97 (Windows/Linux) or below 25.0.1364.99 (Mac), or if they have custom applications bundling a vulnerable ICU library from that time period.
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. Organizations using ICU library in custom applications should also update to a patched ICU version.
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-0900 — 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-0900 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