dbcve.org
ChromeWeb browser · Google

CVE-2011-1295

HIGH · 7.5 CVSS v2.0 Published 2011-03-25
Fix available
A fix is available. Upgrade to 5.0 / 5.0.6 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
WebKit, as used in Google Chrome before 10.0.648.204 and Apple Safari before 5.0.6, does not properly handle node parentage, which allows remote attackers to cause a denial of service (DOM tree corruption), conduct cross-site scripting (XSS) attacks, or possibly have unspecified other impact via unknown vectors.

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 · moderate confidence

A vulnerability in WebKit's DOM handling fails to properly manage node parentage relationships, allowing remote attackers to corrupt the DOM tree, potentially enabling cross-site scripting attacks or causing denial of service through memory corruption.

MitigationUpdate Google Chrome to version 10.0.648.204 or later, and Apple Safari to version 5.0.6 or later. Apply vendor patches for other WebKit-based browsers.

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:< 10.0.648.204
SafariWeb browser
Affected:< 5.0.6
Iphone OsOperating system
Affected:< 5.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. Identify your WebKit-based browser
    Determine if you are using Google Chrome, Apple Safari, or another WebKit-based browser on the system
    Affected if Using Chrome, Safari, or any WebKit-based browser on this system
  2. Check Google Chrome version
    Navigate to chrome://settings or type 'about:version' in the address bar to view the full version number (e.g., 10.0.648.204)
    Affected if Chrome version is lower than 10.0.648.204
  3. Check Apple Safari version
    Open Safari, then go to Safari > About Safari to view the version number (e.g., 5.0.6)
    Affected if Safari version is lower than 5.0.6 on macOS or Windows
  4. Check Apple iOS version
    On iPhone, go to Settings > General > About to view the iOS version
    Affected if iOS version is lower than 5.0

You are affected if you are running a WebKit-based browser (Chrome, Safari) or iOS device with a version lower than the affected ranges listed above.

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 5.0 / 5.0.6 / 10.0.648.204 or later
Fixed in 5.05.0.610.0.648.204
Interim mitigation

Update Google Chrome to version 10.0.648.204 or later, and Apple Safari to version 5.0.6 or later. Apply vendor patches for other WebKit-based browsers.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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