Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a n/a
n/aaffected
References
- http://lists.opensuse.org/opensuse-security-announce/2016-07/msg00021.html ↗
- http://lists.opensuse.org/opensuse-security-announce/2016-07/msg00022.html ↗
- http://googlechromereleases.blogspot.com/2016/07/stable-channel-update.html ↗
- http://www.ubuntu.com/usn/USN-3041-1 ↗
- http://lists.opensuse.org/opensuse-security-announce/2016-07/msg00028.html ↗
- https://crbug.com/610600 ↗
- https://codereview.chromium.org/2069853002/ ↗
- http://lists.opensuse.org/opensuse-security-announce/2016-07/msg00020.html ↗
- http://rhn.redhat.com/errata/RHSA-2016-1485.html ↗
- http://www.securitytracker.com/id/1036428 ↗
- http://www.debian.org/security/2016/dsa-3637 ↗