Description
Multiple serious vulnerabilities have been found in Google Chrome. Malicious users can exploit these vulnerabilities to cause denial of service, spoof user interface, bypass security restrictions and obtain sensitive information.
Below is a complete list of vulnerabilities
- Multiple unknown vulnerabilities can be exploited to cause denial of service or possibly have another unknown impact;
- Comparison operators mishandling at V8 can be exploited remotely via a specially designed JavaScript to obtain sensitive information;
- Subframe navigation mishandling can be exploited remotely via a specially designed web site to spoof address bar;
- Data structure mishandle at V8 can be exploited remotely via a specially designed web site to cause denial of service or have another unknown impact;
- Lack of fallback execution restrictions can be exploited remotely to cause denial of service or have another unknown impact;
- Lack of security restrictions at Blink can be exploited remotely via a specially designed web site to cause denial of service or have another unknown impact;
- Assertion mishandling can be exploited remotely via a specially designed web site to cause denial of service or have another unspecified impact;
- An unknown vulnerability in Skia can be exploited remotely to bypass security restrictions (the Same Origin Policy) and obtain sensitive information.
Technical details
Vulnerability (2) related to JSGenericLowering class in compiler/js-generic-lowering.cc.
Vulnerability (3) related to HistoryController::UpdateForCommit function in content/renderer/history_controller.cc which mishandles interaction between subframe forward navigation and other forward navigation.
Vulnerability (4) related to SerializedScriptValue::transferArrayBuffers function in WebKit/Source/bindings/core/v8/SerializedScriptValue.cpp which mishandles certain array-buffer data structures.
Vulnerability (5) related to extensions/renderer/gc_callback.cc which does not prevent fallback execution once the Garbage collection callback has started.
Vulnerability (6) caused by lack of same render process check for frames.
Vulnerability (7) caused by mishandling assertions in the WTF::BitArray and WTF::double_conversion::Vector classes.
Original advisories
Related products
CVE list
- CVE-2016-1666 critical
- CVE-2016-1665 warning
- CVE-2016-1664 warning
- CVE-2016-1663 high
- CVE-2016-1662 critical
- CVE-2016-1661 critical
- CVE-2016-1660 high
- CVE-2016-5168 warning
Read more
Find out the statistics of the vulnerabilities spreading in your region on statistics.securelist.com