dbcve.org
ChromeWeb browser · Google

CVE-2015-1292

MEDIUM · 5.0 CVSS v2.0 Published 2015-09-03
Fix available
A fix is available. Upgrade to after 44.0.2403 or later.
See remediation →
59/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 NavigatorServiceWorker::serviceWorker function in modules/serviceworkers/NavigatorServiceWorker.cpp in Blink, as used in Google Chrome before 45.0.2454.85, allows remote attackers to bypass the Same Origin Policy by accessing a Service Worker.

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 Same Origin Policy bypass vulnerability in Google Chrome's Blink rendering engine (versions before 45.0.2454.85). The flaw exists in the NavigatorServiceWorker::serviceWorker function in the Service Worker implementation, allowing remote attackers to access Service Workers across different origins.

MitigationUpdate Google Chrome to version 45.0.2454.85 or later to remediate this vulnerability. Organizations should deploy browser updates through their patch management infrastructure.

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
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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. Determine installed Chrome version
    Open Google Chrome and navigate to chrome://version, or click the menu icon > Help > About Google Chrome. The version number appears on the first line.
    Affected if The displayed version is 44.0.2403 or earlier (any version below 45.0.2454.85)
  2. Verify Service Worker is enabled
    Open Developer Tools (F12 or Ctrl+Shift+I), go to the Application tab, and expand the Service Workers section in the left sidebar. Alternatively, navigate to chrome://inspect/#service-workers.
    Affected if Service Workers are enabled and listed as active in the browser (this is the vulnerable component)
  3. Confirm no pending update is available
    In chrome://settings/help, verify if Chrome reports that it is up to date or if an update is available. The vulnerable version is 44.0.2403 and below; version 45.0.2454.85 or later contains the fix.
    Affected if The browser shows a version below 45.0.2454.85 with no update available

You are affected if Google Chrome version 44.0.2403 or earlier is installed and Service Workers feature is enabled in the browser.

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

Update Google Chrome to version 45.0.2454.85 or later to remediate this vulnerability. Organizations should deploy browser updates through their patch management infrastructure.

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-2015-1292 — 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-1292 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