dbcve.org
ChromeWeb browser · Google

CVE-2013-2904

HIGH · 7.5 CVSS v2.0 Published 2013-08-21
Fix available
A fix is available. Upgrade to after 29.0.1547.56 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Use-after-free vulnerability in the Document::finishedParsing function in core/dom/Document.cpp in Blink, as used in Google Chrome before 29.0.1547.57, allows remote attackers to cause a denial of service or possibly have unspecified other impact via an onload event that changes an IFRAME element so that its src attribute is no longer an XML document, leading to unintended garbage collection of this document.

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 confidence

Use-after-free vulnerability in Blink's Document::finishedParsing function. When an onload event changes an IFRAME's src attribute from an XML document to something else, the document can be garbage collected while still in use, leading to a dangling pointer that can be dereferenced.

MitigationUpgrade Google Chrome to version 29.0.1547.57 or later. For embedded Blink implementations, apply the patch to core/dom/Document.cpp to ensure documents are not prematurely garbage collected during the onload event handler 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
Affected:<= 29.0.1547.56= 29.0.1547.0= 29.0.1547.1= 29.0.1547.2= 29.0.1547.3= 29.0.1547.4= 29.0.1547.5= 29.0.1547.7= 29.0.1547.8= 29.0.1547.9= 29.0.1547.10= 29.0.1547.11
Debian LinuxOperating system
Affected:= 7.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' or 'chrome --version' from command line
    Affected if The version displayed is 29.0.1547.0 through 29.0.1547.56, or matches any of these specific versions: 29.0.1547.0, 29.0.1547.1, 29.0.1547.2, 29.0.1547.3, 29.0.1547.4, 29.0.1547.5, 29.0.1547.7, 29.0.1547.8, 29.0.1547.9, 29.0.1547.10, or 29.0.1547.11
  2. Check Chromium version on Debian systems
    Run 'chromium --version' or 'dpkg -l | grep chromium' on Debian Linux to identify the installed browser package and version
    Affected if The system is running Debian 7.0 and the Chromium version matches the affected Chrome 29.0.1547.x range
  3. Verify the vulnerable code path is reachable
    The vulnerability requires a webpage that uses JavaScript in an onload event handler to change an IFRAME's src attribute from an XML document to a different resource type. Check if the browser routinely loads such content
    Affected if The browser environment loads or renders XML documents in IFRAMEs with onload event handlers that modify the IFRAME src attribute

You are affected if you are running Google Chrome version 29.0.1547.0 through 29.0.1547.56 (or any of the specific listed versions) or Debian 7.0 with an equivalent Chromium version, and the browser can render XML documents in IFRAMEs with onload handlers that change the src attribute.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 29.0.1547.56
Interim mitigation

Upgrade Google Chrome to version 29.0.1547.57 or later. For embedded Blink implementations, apply the patch to core/dom/Document.cpp to ensure documents are not prematurely garbage collected during the onload event handler execution.

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2904 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-2904 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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