ChromeWeb browser · Google
CVE-2016-1622
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 · uneditedThe Extensions subsystem in Google Chrome before 48.0.2564.109 does not prevent use of the Object.defineProperty method to override intended extension behavior, which allows remote attackers to bypass the Same Origin Policy via crafted JavaScript code.
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 confidenceA vulnerability in Chrome's Extensions subsystem allows JavaScript code to use Object.defineProperty to override intended extension behavior, enabling attackers to bypass the Same Origin Policy and access cross-origin resources. This affects Chrome versions prior to 48.0.2564.109.
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
<= 48.0.2564.103
Debian LinuxOperating system
= 8.0= 13.1CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Chrome version on Windows or MacNavigate to chrome://settings/help or click Menu > Help > About Google Chrome to display the current version numberAffected if The displayed version is 48.0.2564.103 or earlier
-
Determine installed Chrome version on LinuxOpen a terminal and run: google-chrome --version or chrome --versionAffected if The displayed version is 48.0.2564.103 or earlier
-
Check Chrome version on Debian Linux 8.0Run: dpkg -l | grep google-chrome or check /opt/google/chrome/google-chrome --versionAffected if Chrome version installed via package management is 48.0.2564.103 or earlier on Debian 8.0
-
Check Chrome version on OpenSUSE 13.1Run: rpm -qi google-chrome or zypper info google-chromeAffected if Chrome version installed via package management is 48.0.2564.103 or earlier on OpenSUSE 13.1
-
Confirm extensions subsystem is in useThis vulnerability affects the Extensions subsystem which is a core Chrome component enabled by default; no additional configuration check required for standard browser usageAffected if The browser has any extensions installed or uses internal Chrome extensions (which is the default state)
A system is affected if Google Chrome version is 48.0.2564.103 or earlier, regardless of operating system, as the vulnerability resides in the browser's Extensions subsystem which is enabled by default.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Google Chrome to version 48.0.2564.109 or later to patch the Extensions subsystem. Organizations should ensure enterprise browser deployments are current.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-1622 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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