ChromeWeb browser · Google
CVE-2013-2902
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 the XSLT ProcessingInstruction implementation 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 vectors related to an applyXSLTransform call involving (1) an HTML document or (2) an xsl:processing-instruction element that is still in the process of loading.
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 XSLT ProcessingInstruction implementation allows remote attackers to cause denial of service or potentially execute arbitrary code via vectors involving applyXSLTransform calls with HTML documents or xsl:processing-instruction elements that are still loading. The browser attempts to access freed memory when processing these XSLT transformations.
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
<= 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
= 7.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
- 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 installed Chrome versionOpen Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number will be displayed on that page.Affected if The displayed version is 29.0.1547.56 or lower, or any version from 29.0.1547.0 through 29.0.1547.11 inclusive.
-
Check Chrome version via command lineOn systems with Chrome installed, run 'google-chrome --version' or 'chrome --version' in a terminal.Affected if The reported version matches 29.0.1547.x where x is 0-11, or is 29.0.1547.56 or lower.
-
Verify Debian Chrome package versionOn Debian systems, run 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable' to see the installed package version.Affected if The installed package version is 29.0.1547.56-1 or lower, indicating an unpatched Chrome on Debian 7.0.
-
Confirm XSLT processing capabilityThe vulnerability exists in Blink's XSLT processing. This feature is enabled by default in Chrome and requires no special configuration.Affected if The browser processes XSLT stylesheets; the flaw triggers when applying XSL transformations to documents or xsl:processing-instruction elements still loading.
You are affected if Google Chrome version is 29.0.1547.56 or lower, or any version from 29.0.1547.0 through 29.0.1547.11 inclusive.
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 29.0.1547.57 or later to patch the vulnerability. Organizations should deploy the updated browser version across affected endpoints.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2902 — 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-2902 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