CVE-2016-1706 - CVE House
Back to Database
Status published Critical CVE-2016-1706

The PPAPI implementation in Google Chrome before 52.0.2743.82 does not...

Vulnerability 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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2016-1706

Credits & Attribution

No credits recorded in the NVD database.

References

More from google

View All →
CVE-2025-24959
Environment Variable Injection for dotenv API in zx
Low 1
CVE-2024-45601
Local file Inclusion via static file serving functionality in Mesop
High 7.5
CVE-2022-3708
Web Stories <= 1.24.0 - Server Side Request Forgery
Critical 9.6
CVE-2022-31055
Improper Access Control in kctf
High 7.5
CVE-2022-23569
`CHECK`-fails when building invalid tensor shapes in Tensorflow
Medium 6.5

Affected Vendor

Affected Software

chrome
Vulnerable Versions:
0

Timeline

Official Publish: July 23rd, 2016
Last Modified: August 5th, 2024
Added to House: July 20th, 2026

CVSS Vectors

V3: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.