CVE-2016-1663: Use After Free
A use-after-free flaw was found in the Blink's V8 bindings in the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=603987
External References:
http://googlechromereleases.blogspot.com/2016/04/stable-channel-update28.html
Other sources
The SerializedScriptValue::transferArrayBuffers function in WebKit/Source/bindings/core/v8/SerializedScriptValue.cpp in the V8 bindings in Blink, as used in Google Chrome before 50.0.2661.94, mishandles certain array-buffer data structures, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted web site.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/Chrometo a version that resolves this vulnerability.Fixed in 50.0.2661.94 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 50.0.2661.94
Event History
Frequently Asked Questions
What is the severity of CVE-2016-1663?
CVE-2016-1663 has been classified with high severity due to its potential to cause a denial of service.
How do I fix CVE-2016-1663?
To fix CVE-2016-1663, update Google Chrome to version 50.0.2661.94 or later.
What versions of Google Chrome are affected by CVE-2016-1663?
CVE-2016-1663 affects Google Chrome versions prior to 50.0.2661.94.
Which operating systems are impacted by CVE-2016-1663?
CVE-2016-1663 affects multiple operating systems including openSUSE 13.1 and various editions of Red Hat Enterprise Linux 6.0.
Can exploiting CVE-2016-1663 lead to data leakage?
Exploiting CVE-2016-1663 primarily leads to a denial of service and does not directly result in data leakage.