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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
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 |
References
History
No history.
Status: PUBLISHED
Assigner: Chrome
Published:
Updated: 2024-08-05T23:02:13.379Z
Reserved: 2016-01-12T00:00:00.000Z
Link: CVE-2016-1706
No data.
Status : Modified
Published: 2016-07-23T19:59:01.590
Modified: 2026-05-06T22:30:45.220
Link: CVE-2016-1706
OpenCVE Enrichment
No data.
Weaknesses
Debian DSA
EUVD
Ubuntu USN