CVE-2016-1666: Critical severity redhat Enterprise Linux Desktop Supplementary vulnerability

Published Apr 28, 2016
·
Updated

Multiple unspecified vulnerabilities in Google Chrome before 50.0.2661.94 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=607652

External References:

http://googlechromereleases.blogspot.com/2016/04/stable-channel-update28.html

— Red Hat

Affected Software

7 affected componentsFixes available
redhat Enterprise Linux Desktop Supplementary=6.0
redhat Enterprise Linux Server Supplementary=6.0
redhat Enterprise Linux Server Supplementary Eus=6.7z
redhat Enterprise Linux Workstation Supplementary=6.0
openSUSE openSUSE=13.1
Google Chrome<=50.0.2661.87
redhat/chrome<50.0.2661.94
50.0.2661.94

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/Chrome to a version that resolves this vulnerability.

    Fixed in 50.0.2661.94
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 50.0.2661.94

Event History

Apr 28, 2016
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeakness
Apr 29, 2016
Data Sourced
via Red Hat·07:04 AM
DescriptionSeverityAffected Software
May 14, 2016
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2016-1666?

CVE-2016-1666 is classified as a high severity vulnerability that can lead to denial of service attacks.

2

How do I fix CVE-2016-1666?

To fix CVE-2016-1666, update Google Chrome to version 50.0.2661.94 or later.

3

What versions of Google Chrome are affected by CVE-2016-1666?

CVE-2016-1666 affects Google Chrome versions prior to 50.0.2661.94.

4

Can CVE-2016-1666 be exploited remotely?

Yes, CVE-2016-1666 can be exploited remotely, allowing attackers to cause a denial of service.

5

What are the possible impacts of CVE-2016-1666?

The possible impacts of CVE-2016-1666 include denial of service and potentially other unspecified impacts.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203