Enterprise Linux Desktop SupplementaryOperating system · Redhat
CVE-2016-1665
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 JSGenericLowering class in compiler/js-generic-lowering.cc in Google V8, as used in Google Chrome before 50.0.2661.94, mishandles comparison operators, which allows remote attackers to obtain sensitive information 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 confidenceThe JSGenericLowering class in compiler/js-generic-lowering.cc in Google V8 mishandles comparison operators, allowing crafted JavaScript code to potentially obtain sensitive information through improper memory access or information disclosure.
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
- 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 Google Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminal to see the installed Chrome versionAffected if Version is 50.0.2661.87 or earlier (versions before 50.0.2661.94)
-
Check V8 JavaScript engine version embedded in ChromeOpen Chrome, navigate to chrome://version, look for the V8 version string in the JavaScript engine fieldAffected if V8 version corresponds to Chrome 50.0.2661.87 or earlier releases
-
Check for V8 on Linux systems with Chromium/Chrome packagesRun 'rpm -qa | grep -i v8' or 'dpkg -l | grep -i v8' to list installed V8 packages, then run 'v8-version' or check package details for version numberAffected if V8 package version is 5.0.71.0 or earlier (the version shipped with Chrome 50.0.2661.87)
-
Identify if running Red Hat Enterprise Linux 6.x SupplementaryRun 'cat /etc/redhat-release' to confirm the OS version and 'rpm -qa | grep -i chrome' to check for installed Chrome packagesAffected if System is RHEL 6.0, 6.7, or 6.z Supplementary with Chrome version <= 50.0.2661.87
User is affected if Google Chrome version is 50.0.2661.87 or earlier, or if the embedded V8 engine version is equivalent to that Chrome release, or if RHEL 6 Supplementary has the vulnerable Chrome/V8 package installed.
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 dataUpgrade Google Chrome to version 50.0.2661.94 or later to include the patched V8 JavaScript engine.
Fix this in Enterprise Linux Desktop Supplementary
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1665 — 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-1665 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