CVE-2016-1695: High severity Google Chrome vulnerability
Multiple unspecified vulnerabilities in Google Chrome before 51.0.2704.63 allow attackers to cause a denial of service or possibly have other impact via unknown vectors.
Other sources
Various fixes from internal audits, fuzzing and other initiatives.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=614767
External References:
http://googlechromereleases.blogspot.com/2016/05/stable-channel-update25.html
— Red Hat
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2016-1672
- CVE-2016-1673
- CVE-2016-1674
- CVE-2016-1675
- CVE-2016-1676
- CVE-2016-1677
- CVE-2016-1678
- CVE-2016-1679
- CVE-2016-1680
- CVE-2016-1681
- CVE-2016-1682
- CVE-2016-1683
- CVE-2016-1684
- CVE-2016-1685
- CVE-2016-1686
- CVE-2016-1687
- CVE-2016-1688
- CVE-2016-1689
- CVE-2016-1690
- CVE-2016-10403
- CVE-2016-1691
- CVE-2016-1692
- CVE-2016-1693
- CVE-2016-1694
Frequently Asked Questions
What is the severity of CVE-2016-1695?
CVE-2016-1695 has not been assigned a specific CVSS score, but it allows for denial of service and potentially other impacts.
How do I fix CVE-2016-1695?
To fix CVE-2016-1695, you should upgrade to Google Chrome version 51.0.2704.63 or later.
What versions of Google Chrome are affected by CVE-2016-1695?
CVE-2016-1695 affects all versions of Google Chrome prior to version 51.0.2704.63.
Are there any other software affected by CVE-2016-1695?
CVE-2016-1695 primarily affects Google Chrome and has specific implications on multiple Linux distributions that run earlier versions.
Can CVE-2016-1695 be exploited remotely?
Yes, CVE-2016-1695 can potentially be exploited remotely to cause a denial of service.