CVE-2016-1706
Published: 23 July 2016
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.
Priority
Status
Package | Release | Status |
---|---|---|
chromium-browser Launchpad, Ubuntu, Debian |
precise |
Ignored
|
trusty |
Released
(52.0.2743.116-0ubuntu0.14.04.1.1134)
|
|
upstream |
Released
(52.0.2743.82)
|
|
wily |
Ignored
(end of life)
|
|
xenial |
Released
(52.0.2743.116-0ubuntu0.16.04.1.1250)
|
|
yakkety |
Released
(53.0.2785.143-0ubuntu1.1307)
|
|
oxide-qt Launchpad, Ubuntu, Debian |
precise |
Does not exist
|
trusty |
Released
(1.16.5-0ubuntu0.14.04.1)
|
|
upstream |
Released
(1.16.5)
|
|
wily |
Ignored
(end of life)
|
|
xenial |
Released
(1.16.5-0ubuntu0.16.04.1)
|
|
yakkety |
Released
(1.16.7-0ubuntu1)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 9.6 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | Required |
Scope | Changed |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |