Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.6

Google Chrome before 52 allows sandbox bypass

CVE-2016-1706 · published 10 years ago
Summary

Versions of Google Chrome earlier than 52 can be tricked into accepting messages from the wrong source, letting attackers bypass the browser’s sandbox protection. This could let malicious code run with higher privileges than intended. Update Chrome to version 52.0.2743.82 or later to fix the issue.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
google chrome <= 51.0.2704.106
cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
Original advisory text
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 ...
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.
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit (estimated)
  • Gives an attacker full control (estimated)
Severity
9.6 Critical
Exploitation
2% chance of attack within 30 days
Type
CWE-20Improper Input Validation
Timeline
Published23 Jul 2016
Updated4 Nov 2026
First seen29 Sep 2026
Sources
CVE-2016-1706 · NVD
Track software like this
Free during beta