What is the severity of CVE-2016-1668?

CVE-2016-1668 is classified as a high severity vulnerability.

How do I fix CVE-2016-1668?

To fix CVE-2016-1668, users should update Google Chrome to version 50.0.2661.102 or higher, or apply the relevant patches for affected operating systems.

What does CVE-2016-1668 exploit?

CVE-2016-1668 exploits an improper creation context in the V8 bindings in Blink, allowing attackers to bypass the Same Origin Policy.

Which versions of Google Chrome are affected by CVE-2016-1668?

CVE-2016-1668 affects Google Chrome versions prior to 50.0.2661.102.

Can CVE-2016-1668 impact other operating systems besides Google Chrome?

Yes, CVE-2016-1668 also affects openSUSE 13.1 and Debian GNU/Linux version 8.0.

Vulnerability/
CVE-2016-1668

high

8.8

CWE

284

14/5/2016

5/8/2024

CVE-2016-1668

First published: Sat May 14 2016(Updated: )

The forEachForBinding function in WebKit/Source/bindings/core/v8/Iterable.h in the V8 bindings in Blink, as used in Google Chrome before 50.0.2661.102, uses an improper creation context, which allows remote attackers to bypass the Same Origin Policy via a crafted web site.

Credit: cve-coordination@google.com

Affected Software	Affected Version	How to fix
Google Chrome	<=50.0.2661.87
openSUSE	=13.1
Debian GNU/Linux	=8.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-1668?
CVE-2016-1668 is classified as a high severity vulnerability.
How do I fix CVE-2016-1668?
To fix CVE-2016-1668, users should update Google Chrome to version 50.0.2661.102 or higher, or apply the relevant patches for affected operating systems.
What does CVE-2016-1668 exploit?
CVE-2016-1668 exploits an improper creation context in the V8 bindings in Blink, allowing attackers to bypass the Same Origin Policy.
Which versions of Google Chrome are affected by CVE-2016-1668?
CVE-2016-1668 affects Google Chrome versions prior to 50.0.2661.102.
Can CVE-2016-1668 impact other operating systems besides Google Chrome?
Yes, CVE-2016-1668 also affects openSUSE 13.1 and Debian GNU/Linux version 8.0.

agent/type
agent/references
agent/author
agent/weakness
agent/severity
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/google
canonical/google chrome
version/google chrome/50.0.2661.87
vendor/opensuse
canonical/opensuse
version/opensuse/13.1
vendor/debian
canonical/debian gnu/linux
version/debian gnu/linux/8.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-1668?
CVE-2016-1668 is classified as a high severity vulnerability.
How do I fix CVE-2016-1668?
To fix CVE-2016-1668, users should update Google Chrome to version 50.0.2661.102 or higher, or apply the relevant patches for affected operating systems.
What does CVE-2016-1668 exploit?
CVE-2016-1668 exploits an improper creation context in the V8 bindings in Blink, allowing attackers to bypass the Same Origin Policy.
Which versions of Google Chrome are affected by CVE-2016-1668?
CVE-2016-1668 affects Google Chrome versions prior to 50.0.2661.102.
Can CVE-2016-1668 impact other operating systems besides Google Chrome?
Yes, CVE-2016-1668 also affects openSUSE 13.1 and Debian GNU/Linux version 8.0.