dbcve.org
ChromeWeb browser · Google

CVE-2013-2911

MEDIUM · 6.8 CVSS v2.0 Published 2013-10-02
Fix available
A fix is available. Upgrade to after 30.0.1599.65 or later.
See remediation →
77/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 XSLStyleSheet::compileStyleSheet function in core/xml/XSLStyleSheetLibxslt.cpp in Blink, as used in Google Chrome before 30.0.1599.66, allows remote attackers to cause a denial of service or possibly have unspecified other impact by leveraging improper handling of post-failure recompilation in unspecified libxslt versions.

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 XSLStyleSheet::compileStyleSheet function allows remote attackers to cause denial of service or possibly execute arbitrary code by triggering improper handling of post-failure recompilation in libxslt versions.

MitigationUpdate Google Chrome to version 30.0.1599.66 or later to patch the vulnerable Blink rendering engine component.

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:<= 30.0.1599.65= 30.0.1599.0= 30.0.1599.1= 30.0.1599.2= 30.0.1599.4= 30.0.1599.5= 30.0.1599.6= 30.0.1599.7= 30.0.1599.8= 30.0.1599.9= 30.0.1599.10= 30.0.1599.11

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

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

  1. Verify Google Chrome is installed
    Check if Google Chrome browser is present on the system. On Windows, look for Chrome in Program Files or the registry. On macOS, check /Applications/Google Chrome.app. On Linux, check for google-chrome package or binary.
    Affected if Google Chrome is not installed - the vulnerability only affects Google Chrome with the Blink rendering engine.
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' on Linux, or check the About dialog via the Chrome menu.
    Affected if The version cannot be determined - you need to confirm the exact version number to assess exposure.
  3. Compare version against affected range
    Compare the installed version number to the affected range: 30.0.1599.0 through 30.0.1599.65. Note that versions 30.0.1599.12 through 30.0.1599.65 are also affected based on the '<=30.0.1599.65' specification.
    Affected if The installed version falls within 30.0.1599.0 to 30.0.1599.65 inclusive - this indicates the environment is running a vulnerable version.
  4. Confirm Blink/XSLT processing context
    The vulnerability is triggered through improper handling of post-failure recompilation in libxslt when processing XSL stylesheets. Users who do not process untrusted XSLT content may have reduced exposure.
    Affected if The user processes XSL stylesheets in Chrome - this is the specific feature (XSLStyleSheet::compileStyleSheet) that contains the use-after-free vulnerability.

If Google Chrome is installed and the version is 30.0.1599.65 or earlier (specifically 30.0.1599.0 through 30.0.1599.65), the environment is affected by this CVE.

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 30.0.1599.65
Interim mitigation

Update Google Chrome to version 30.0.1599.66 or later to patch the vulnerable Blink rendering engine component.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2911 — 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-2911 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