dbcve.org
ChromeWeb browser · Google

CVE-2015-1303

HIGH · 7.5 CVSS v2.0 Published 2015-10-12
Fix available
A fix is available. Upgrade to after 45.0.2454.93 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
bindings/core/v8/V8DOMWrapper.h in Blink, as used in Google Chrome before 45.0.2454.101, does not perform a rethrow action to propagate information about a cross-context exception, which allows remote attackers to bypass the Same Origin Policy via a crafted HTML document containing an IFRAME element.

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

A vulnerability in Blink's V8 DOM wrapper (V8DOMWrapper.h) fails to properly propagate cross-context exceptions, allowing the Same Origin Policy to be bypassed. Attackers can use crafted HTML with an IFRAME element to access information across different origins by exploiting the improper exception handling.

MitigationUpdate Google Chrome to version 45.0.2454.101 or later to patch this vulnerability. Ensure browser update policies are enforced organization-wide.

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

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 Chrome version via browser UI
    Open Google Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.
    Affected if The displayed version is 45.0.2454.93 or lower.
  2. Check Chrome version via address bar
    Type chrome://version in the address bar and press Enter. Locate the 'Profile path' line - the version number appears at the top of this page.
    Affected if The version shown is 45.0.2454.93 or earlier.
  3. Check Chrome version via command line (Windows)
    Open Command Prompt and run: reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version
    Affected if The version value returned is 45.0.2454.93 or lower.
  4. Check Chrome version via command line (Mac)
    Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
    Affected if The version output is 45.0.2454.93 or lower.

If any of the above checks show Google Chrome version 45.0.2454.93 or lower, the browser is affected by this Same Origin Policy bypass vulnerability.

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

Update Google Chrome to version 45.0.2454.101 or later to patch this vulnerability. Ensure browser update policies are enforced organization-wide.

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-1303 — 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-1303 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