Debian LinuxOperating system · Debian
CVE-2016-1687
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 renderer implementation in Google Chrome before 51.0.2704.63 does not properly restrict public exposure of classes, which allows remote attackers to obtain sensitive information via vectors related to extensions.
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 confidenceThe Chrome renderer implementation before version 51.0.2704.63 improperly exposes internal classes to extensions, allowing extension-based attack vectors to leak sensitive information from the renderer process.
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
Debian LinuxOperating system
= 8.0
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
ChromeWeb browser
<= 50.0.2661.102= 42.1= 13.2= 12.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionOpen Chrome, go to chrome://settings/help, or run 'google-chrome --version' or 'chromium --version' from command lineAffected if Version is 50.0.2661.102 or earlier (any version <= 50.0.2661.102)
-
Verify if running on affected Debian versionCheck /etc/debian_version file or run 'cat /etc/os-release' to confirm Debian 8.0Affected if System is Debian 8.0 and Chrome <= 50.0.2661.102 is installed
-
Verify if running on affected RHEL/CentOS versionRun 'cat /etc/redhat-release' to check if version 6.0Affected if System is RHEL 6.0 (or CentOS 6.0 equivalent) and Chrome <= 50.0.2661.102 is installed
-
Verify if running on affected openSUSE versionRun 'cat /etc/os-release' to check version 42.1 or 13.2Affected if System is openSUSE 42.1 or 13.2 and Chrome <= 50.0.2661.102 is installed
-
Verify if running on affected SUSE Linux Enterprise versionRun 'cat /etc/os-release' to check if version 12.0Affected if System is SUSE Linux Enterprise 12.0 and Chrome <= 50.0.2661.102 is installed
-
Confirm extension framework is accessibleCheck if Chrome extensions can be installed or are enabled by navigating to chrome://extensions/Affected if Extensions are enabled or can be installed in the browser
You are affected if Google Chrome version is 50.0.2661.102 or earlier on any of the listed Linux distributions (Debian 8.0, RHEL 6.0, openSUSE 42.1/13.2, or SLE 12.0), especially when the extension framework is accessible.
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 51.0.2704.63 or later to remediate the class exposure vulnerability in the renderer.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1687 — 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-1687 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