dbcve.org
ChromeWeb browser · Google

CVE-2015-1291

MEDIUM · 6.4 CVSS v2.0 Published 2015-09-03
Fix available
A fix is available. Upgrade to after 44.0.2403 or later.
See remediation →
73/100
Remediation priority · Elevated
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
The ContainerNode::parserRemoveChild function in core/dom/ContainerNode.cpp in Blink, as used in Google Chrome before 45.0.2454.85, does not check whether a node is expected, which allows remote attackers to bypass the Same Origin Policy or cause a denial of service (DOM tree corruption) via a web site with crafted JavaScript code and IFRAME elements.

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

The ContainerNode::parserRemoveChild function in Blink's DOM implementation fails to validate whether a node being removed is an 'expected' node during parsing. This allows crafted JavaScript with IFRAME elements to manipulate the DOM in ways that violate the Same Origin Policy (enabling potential cross-origin data access) or corrupt the DOM tree, causing denial of service.

MitigationUpgrade Google Chrome to version 45.0.2454.85 or later. No server-side mitigations are available as this is a client-side browser vulnerability.

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:<= 44.0.2403

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
None
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:N/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 Google Chrome version
    Open Chrome, click the three-dot menu in the top-right, select 'Help', then 'About Google Chrome'. The version number is displayed on that page.
    Affected if The displayed version is 44.0.2403 or lower
  2. Confirm Chrome channel (optional)
    In the About Chrome page, look for the channel indicator (Stable, Beta, Dev, Canary) next to the version number.
    Affected if Any channel showing an affected version, though Stable is the primary affected channel
  3. Verify Blink-based browser variant
    This vulnerability is in the Blink rendering engine. Confirm the affected browser is Google Chrome (or a Chromium-based browser using the same Blink version).
    Affected if Running Google Chrome or a Chromium-based browser with Blink version corresponding to Chrome 44.0.2403 or earlier

If Google Chrome version is 44.0.2403 or lower, the browser is vulnerable to Same Origin Policy bypass and DOM corruption via crafted JavaScript with IFRAME elements during parsing.

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

Upgrade Google Chrome to version 45.0.2454.85 or later. No server-side mitigations are available as this is a client-side browser vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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