ChromeWeb browser · Google
CVE-2013-6625
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 core/dom/ContainerNode.cpp in Blink, as used in Google Chrome before 31.0.1650.48, allows remote attackers to cause a denial of service or possibly have unspecified other impact by leveraging improper handling of DOM range objects in circumstances that require child node removal after a (1) mutation or (2) blur event.
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 Blink's ContainerNode.cpp where DOM range objects are improperly handled during child node removal after mutation or blur events. This allows freed memory to be accessed, potentially leading to denial of service or arbitrary code execution.
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
<= 31.0.1650.47= 31.0.1650.0= 31.0.1650.2= 31.0.1650.3= 31.0.1650.4= 31.0.1650.5= 31.0.1650.6= 31.0.1650.7= 31.0.1650.8= 31.0.1650.9= 31.0.1650.10= 31.0.1650.11CVSS 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 Chrome versionOpen chrome://version in the Chrome browser or run 'google-chrome --version' from command lineAffected if The version listed is 31.0.1650.0 through 31.0.1650.47, or specifically 31.0.1650.0, 31.0.1650.2, 31.0.1650.3, 31.0.1650.4, 31.0.1650.5, 31.0.1650.6, 31.0.1650.7, 31.0.1650.8, 31.0.1650.9, 31.0.1650.10, or 31.0.1650.11
-
Confirm browser engine is BlinkNavigate to chrome://version and look for 'Blink' in the UI version string or check the application user agentAffected if The browser is Google Chrome using the Blink rendering engine (this is the default for Chrome 31)
-
Identify if DOM manipulation with range objects occursThis vulnerability triggers when JavaScript code removes child nodes from DOM elements while range objects referencing those nodes exist, particularly after mutation events or blur eventsAffected if The user runs any web content that performs DOM range operations combined with node removal after mutation or blur events
You are affected if you are running Google Chrome version 31.0.1650.0 through 31.0.1650.47 (including the specifically listed versions 31.0.1650.0-11) and you process web content that uses DOM range manipulation alongside node removal after mutation or blur events.
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 dataUpgrade Google Chrome to version 31.0.1650.48 or later. For embedded Blink implementations, apply the corresponding patch to core/dom/ContainerNode.cpp that fixes proper reference handling during DOM range operations.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,496.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6625 — 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-6625 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