CVE-2016-1629: Critical severity google chrome vulnerability
Published Feb 21, 2016
·Updated
Google Chrome before 48.0.2564.116 allows remote attackers to bypass the Blink Same Origin Policy and a sandbox protection mechanism via unspecified vectors.
Affected Software
6 affected components
Google Chrome<=48.0.2564.109
Novell Suse Package Hub For Suse Linux Enterprise=12
openSUSE Leap=42.1
openSUSE openSUSE=13.1
openSUSE openSUSE=13.2
Debian Debian Linux=8.0
Event History
Feb 21, 2016
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2016-1629?
CVE-2016-1629 is rated as a high severity vulnerability due to its potential to allow remote attackers to bypass security protections.
2
How do I fix CVE-2016-1629?
To fix CVE-2016-1629, upgrade Google Chrome to version 48.0.2564.116 or later.
3
What type of attacks can CVE-2016-1629 enable?
CVE-2016-1629 can enable remote attackers to bypass the Blink Same Origin Policy and sandbox protections.
4
Which versions of Google Chrome are affected by CVE-2016-1629?
Google Chrome versions prior to 48.0.2564.116 are affected by CVE-2016-1629.
5
Are any other software products affected by CVE-2016-1629?
CVE-2016-1629 also affects certain versions of SUSE Package Hub for SUSE Linux Enterprise and openSUSE.