Vulnerabilities · 2016 · Google
CVE-2016-1706
Google Chrome vulnerability
The PPAPI implementation in Google Chrome before 52.0.2743.82 does not validate the origin of IPC messages to the plugin broker process that should have come from the browser process, which allows remote attackers to bypass a sandbox protection mechanism via an unexpected message type, related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
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/07/stable-channel-update.html
- lists.opensuse.org/opensuse-security-announce/2016-07/msg00020.html
- lists.opensuse.org/opensuse-security-announce/2016-07/msg00021.html
- lists.opensuse.org/opensuse-security-announce/2016-07/msg00022.html
- lists.opensuse.org/opensuse-security-announce/2016-07/msg00028.html
- rhn.redhat.com/errata/RHSA-2016-1485.html
- www.debian.org/security/2016/dsa-3637
- www.securitytracker.com/id/1036428
- nvd.nist.gov/vuln/detail/CVE-2016-1706
- cve.org/CVERecord?id=CVE-2016-1706
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.