Cloudanix VulnDB

CVE-2015-1303

None

CVSS

—

EPSS

1.7%

Published

Oct 12, 2015

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A flaw in an older version of Chrome could let a malicious webpage peek at or change information from another website the user visited.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Data Exposure
Component
Web Framework
Class
Improper Input Validation
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Failure to rethrow cross-context exceptions in V8DOMWrapper allows unhandled exception data to leak across origins, violating Same Origin Policy enforcement for IFRAME content.

Why it matters to the business

Attackers could read or manipulate data belonging to other websites visited by users, resulting in credential theft, session hijacking, or unauthorized actions within the browser.

How an attack unfolds

An attacker serves a crafted HTML page containing a specially constructed IFRAME that triggers a cross-context JavaScript exception; because the rethrow action is omitted, exception details propagate without origin checks, enabling the attacker script to access or influence content from a different origin.

How to fix it

Upgrade Google Chrome to version 45.0.2454.101 or later; ensure automatic updates are enabled and audit any pinned or enterprise-managed deployments for older builds.

How to confirm the fix worked

Verify installed Chrome version is 45.0.2454.101 or newer via chrome://version; test with proof-of-concept HTML containing cross-origin IFRAME exception triggers in a controlled environment to confirm policy enforcement.

Typical attack path

  1. Craft malicious HTML document embedding an IFRAME targeting a victim origin
  2. Host the document on attacker-controlled site or deliver via phishing/malvertising
  3. Victim browser loads the page and executes the IFRAME content
  4. Trigger cross-context exception that is not properly rethrown
  5. Bypass Same Origin Policy to read or alter cross-origin data

How to detect it

Search web proxy or browser telemetry logs for requests to attacker domains serving IFRAME-heavy pages around the time of suspected exposure; review JavaScript error logs or console output for unexpected cross-origin exception artifacts; no public exploit code or specific IOCs are known.

What your security team should do

  • Prioritize update of all Chrome instances to 45.0.2454.101+ within 30 days given stable but non-zero EPSS
  • Enable enterprise update policies and monitor for unpatched endpoints via inventory scans
  • Review web application code for reliance on IFRAME cross-origin isolation as a control

The record

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.

Affected packages

Ecosystem Package Introduced Fixed
Debian:8 chromium-browser 0 46.0.2490.71-1~deb8u1
Mageia:5 chromium-browser-stable 0 45.0.2454.101-1.mga5
Red Hat:rhel_extras:6 chromium-browser 0 0:45.0.2454.101-1.el6
Red Hat:rhel_extras:6 chromium-browser-debuginfo 0 0:45.0.2454.101-1.el6
Ubuntu:14.04:LTS chromium-browser 0 45.0.2454.101-0ubuntu0.14.04.1.1099
Ubuntu:14.04:LTS oxide-qt 0 1.9.5-0ubuntu0.14.04.1
openSUSE:Tumbleweed chromium 0 55.0.2883.75-3.1
openSUSE:Tumbleweed chromium 0 113.0.5672.92-1.1

Related vulnerabilities