Дата обнаружения
|
20/07/2016 |
Уровень угрозы
|
Critical |
Описание
|
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, execute arbitrary code or obtain sensitive information. Below is a complete list of vulnerabilities
Technical details Vulnerability (1) related to CSPSource::schemeMatches function in WebKit/Source/core/frame/csp/CSPSource.cpp in the Content Security Policy (CSP) implementation which does not apply http policies to https urls and does not apply ws policies to wss urls which makes it easier to determine whether a specific HSTS web site has been visited. Vulnerability (2) related to extensions/renderer/user_script_injector.cc. Vulnerability (3) related to WebKit/Source/core/html/parser/HTMLPreloadScanner.cpp which does not consider referrer-policy information inside an HTML document during a preload request. This vulnerability can be exploited to bypass CSP protection. Vulnerability (4) related to net/proxy/proxy_service.cc which does not ensure that URL information is restricted to a scheme, host, and port . Exploitation of this vulnerability can allow to discover credentials. Vulnerability (5) can be exploited via proxy authentication login prompt. Vulnerability (6) can be exploited via https IFRAME element inside an http IFRAME element. Vulnerability (7) related to the XPointer range-to function. Vulnerability (8) related to content/renderer/history_controller.cc which does not restrict multiple uses of a JavaScript forward method. Vulnerability (9) related to improper handling of left-trimmed objects. Vulnerability (10) related to objects.cc which does not prevent API interceptors from modifying a store target without setting a property. Vulnerability (11) related to WebKit/Source/core/editing/VisibleUnits.cpp and can be triggered via JavaScript code involving an @import at-rule in a Cascading Style Sheets (CSS) token sequence in conjunction with a rel=import attribute of a LINK element. Vulnerability (12) related to ChromeClientImpl::createWindow method in WebKit/Source/web/ChromeClientImpl.cpp which does not prevent window creation by a deferred frame. Vulnerability (13) related to ByteArray::Get method in data/byte_array.cc. Vulnerability (14) related to inline-installation implementation which does not properly consider lifetime. Vulnerability (15) related to ios/web/web_state/ui/crw_web_controller.mm which does not ensure that invalid URL is replaced with the about:blank URL. Vulnerability (16) caused by lack of validation the origin of IPC messages to the plugin broker process that should have come from the browser process. This vulnerability related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc. |
Пораженные продукты
|
Google Chrome versions earlier than 52.0.2743.82 (All branches) |
Решение
|
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. |
Первичный источник обнаружения
|
Google Chrome realases blog |
Оказываемое влияние
?
|
OSI
[?]
DoS
[?]
SB
[?]
SUI
[?]
|
Связанные продукты
|
Google Chrome |
CVE-IDS
|
CVE-2016-51374.3Warning
CVE-2016-51366.8High CVE-2016-51354.3Warning CVE-2016-51344.3Warning CVE-2016-51334.3Warning CVE-2016-51326.8High CVE-2016-51316.8High CVE-2016-51304.3Warning CVE-2016-51296.8High CVE-2016-51286.8High CVE-2016-51276.8High CVE-2016-17116.8High CVE-2016-17106.8High CVE-2016-17096.8High CVE-2016-17086.8High CVE-2016-17074.3Warning CVE-2016-17069.3Critical CVE-2016-17056.8High |
Узнай статистику распространения уязвимостей в твоем регионе |