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.
CVSS Details
- CVSS 3.1 Base Score: 9.6
- CVSS 3.0 Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade chromium-browser | Aug 1, 2016 | Jul 23, 2016 |
| Freebsd | — | Upgrade chromium-npapiUpgrade chromium-pulseUpgrade chromium | Dec 10, 2025 | Jul 22, 2016 |
| Google Chrome | — | Upgrade to the latest version of Google Chrome | Jul 27, 2016 | Jul 20, 2016 |
| Redhat_linux | — | Upgrade chromium-browser-debuginfoUpgrade chromium-browser | Jul 29, 2016 | Jul 23, 2016 |
| Suse | — | Upgrade chromedriverUpgrade chromium-ffmpegsumoUpgrade chromium-desktop-kdeUpgrade chromium-desktop-gnomeUpgrade chromium | Jul 26, 2016 | Jul 23, 2016 |
| Ubuntu | — | Upgrade liboxideqtcore0 | Aug 6, 2016 | Jul 23, 2016 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub