Vulnerabilities · 2016 · Google
CVE-2016-1618
Google Chrome vulnerability
Blink, as used in Google Chrome before 48.0.2564.82, does not ensure that a proper cryptographicallyRandomValues random number generator is used, which makes it easier for remote attackers to defeat cryptographic protection mechanisms via unspecified vectors.
Affected products
Chrome. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Chrome runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- googlechromereleases.blogspot.com/2016/01/stable-channel-update_20.html
- lists.opensuse.org/opensuse-security-announce/2016-01/msg00035.html
- lists.opensuse.org/opensuse-security-announce/2016-01/msg00036.html
- lists.opensuse.org/opensuse-security-announce/2016-01/msg00046.html
- rhn.redhat.com/errata/RHSA-2016-0072.html
- www.debian.org/security/2016/dsa-3456
- www.securityfocus.com/bid/81430
- www.securitytracker.com/id/1034801
- nvd.nist.gov/vuln/detail/CVE-2016-1618
- cve.org/CVERecord?id=CVE-2016-1618
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.