Detect date
?
|
04/28/2016 |
Severity
?
|
Critical |
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
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. |
Affected products
|
Google Chrome versions earlier than 50.0.2661.94 (All branches) |
Solution
|
Update to the latest version. File with name old_chrome can be still detected after update. It caused by Google Chrome update policy which does not remove old versions when installing updates. Try to contact vendor for further delete instructions or ignore such kind of alerts at your own risk. |
Original advisories
|
|
Impacts
?
|
OSI [?] DoS [?] SB [?] SUI [?] |
Related products
|
Google Chrome |
CVE-IDS
?
|
CVE-2016-16667.5Critical
CVE-2016-16654.3Warning CVE-2016-16644.3Warning CVE-2016-16636.8High CVE-2016-16618.3Critical CVE-2016-16606.8High CVE-2016-51685.0Critical |
Find out the statistics of the vulnerabilities spreading in your region |