ChromeWeb browser · Google
CVE-2013-0903
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 · uneditedUse-after-free vulnerability in Google Chrome before 25.0.1364.152 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the handling of browser navigation.
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 confidenceUse-after-free vulnerability in Google Chrome's browser navigation handling before version 25.0.1364.152 allows remote attackers to cause denial of service or potentially achieve code execution by freeing memory and then accessing it after it has been deallocated.
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.126= 25.0.1364.0= 25.0.1364.1= 25.0.1364.2= 25.0.1364.3= 25.0.1364.5= 25.0.1364.7= 25.0.1364.8= 25.0.1364.9= 25.0.1364.10= 25.0.1364.11= 25.0.1364.12CVSS 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 if Google Chrome is installedOn Windows, look for chrome.exe in Program Files or via registry. On Linux, run 'which google-chrome' or check /usr/bin/google-chrome. On Mac, check /Applications/Google Chrome.appAffected if Google Chrome is not installed - the check does not apply
-
Obtain the installed Chrome version numberOpen chrome://version in the Chrome browser, or run 'google-chrome --version' from command line on Linux/Mac, or check the version in Help > About Google Chrome on WindowsAffected if Unable to determine the installed version
-
Compare installed version against affected rangeCheck if version is 25.0.1364.126 or lower, OR matches any of: 25.0.1364.0, .1, .2, .3, .5, .7, .8, .9, .10, .11, .12Affected if Installed version is 25.0.1364.126 or lower, or exactly matches any of the listed point versions (25.0.1364.0 through 25.0.1364.12)
-
Verify Chrome is used for browser navigationThe vulnerability affects the browser navigation handling component - this is always active in any Chrome installation used for web browsingAffected if Chrome is installed and being used for web navigation - the vulnerable component is inherently enabled
If Chrome is installed and its version falls within 25.0.1364.0 to 25.0.1364.126 (including all listed point versions), the environment is affected by this use-after-free vulnerability.
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 dataUpdate Google Chrome to version 25.0.1364.152 or later to patch the vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0903 — 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-0903 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