Enterprise Linux Desktop SupplementaryOperating system · Redhat
CVE-2016-1661
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 · uneditedBlink, as used in Google Chrome before 50.0.2661.94, does not ensure that frames satisfy a check for the same renderer process in addition to a Same Origin Policy check, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted web site, related to BindingSecurity.cpp and DOMWindow.cpp.
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 Same Origin Policy bypass vulnerability in Blink rendering engine (used in Chrome before 50.0.2661.94) allows a malicious website to access cross-origin frames because the code in BindingSecurity.cpp and DOMWindow.cpp does not verify frames are in the same renderer process in addition to the Same Origin Policy check, leading to memory corruption.
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
Enterprise Linux Desktop SupplementaryOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 6.0
Enterprise Linux Server Supplementary EusOperating system
= 6.7z
Enterprise Linux Workstation SupplementaryOperating system
= 6.0
ChromeWeb browser
<= 50.0.2661.87= 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Check if Google Chrome is installedOn Linux: rpm -qa | grep -i chrome or dpkg -l | grep -i chrome. On Windows: Check Program Files\Google\Chrome\Application\chrome.exe exists or check Add/Remove Programs.Affected if Google Chrome browser is installed on the system
-
Determine installed Google Chrome versionOn Linux: google-chrome --version or /opt/google/chrome/chrome --version. On Windows: Right-click chrome.exe > Properties > Details > File version, or run 'chrome.exe --version' from command line.Affected if Version is 50.0.2661.87 or lower (the vulnerable version range)
-
Verify Blink rendering engine is in useThis is automatic when Chrome is running. No separate check needed - Blink is the default rendering engine for Chrome versions in the affected range.Affected if Chrome is running or has been used, as Blink is the default rendering engine for affected versions
If Google Chrome version 50.0.2661.87 or lower is installed and has been used, the system is affected by this Same Origin Policy bypass vulnerability.
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 dataDeploy Google Chrome version 50.0.2661.94 or later across all affected endpoints to remediate the vulnerability; enterprise patch management should enforce this update.
Fix this in Enterprise Linux Desktop Supplementary
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1661 — 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-1661 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