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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Debian DSA |
DSA-3637-1 | chromium-browser security update |
EUVD |
EUVD-2016-2801 | 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. |
Ubuntu USN |
USN-3041-1 | Oxide vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Chrome
Published:
Updated: 2024-08-05T23:02:13.379Z
Reserved: 2016-01-12T00:00:00
Link: CVE-2016-1706
No data.
Status : Deferred
Published: 2016-07-23T19:59:01.590
Modified: 2025-04-12T10:46:40.837
Link: CVE-2016-1706
OpenCVE Enrichment
No data.
Weaknesses
Debian DSA
EUVD
Ubuntu USN