chromium-browser: sandbox escape in ppapi
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 6 Supplementary | |||
| chromium-browser-0:52.0.2743.82-1.el6 | cpe:/a:redhat:rhel_extras:6 | RHSA-2016:1485 | 2016-07-26T00:00:00Z |
No data available yet.
| 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 |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 2.2% (2.178% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.