KLA10776
Multiple vulnerabilities in Google Chrome
Updated: 06/01/2019
Detect date
?
03/24/2016
Severity
?
Critical
Description

Multiple serious vulnerabilities have been found in Google Chrome. Malicious users can exploit these vulnerabilities to cause denial of service or execute arbitrary code.

Below is a complete list of vulnerabilities

  1. Multiple unknown vulnerabilities at V8 can be exploited to cause denial of service or conduct other unknown impact;
  2. An unknown vulnerability can be exploited via vectors related to creating MHTML document to cause denial of service or conduct other unknown impact;
  3. An improper data-type mismatch handling at libANGLE can be exploited remotely via a specially designed specially designed shared stages to cause denial of service or conduct other unknown impact;
  4. Use-after-free vulnerability at Extensions cam be exploited remotely via a specially designed JavaScript code to cause denial of service or conduct other unknown impact;
  5. Use-after-free vulnerability at Navigation can be exploited remotely to cause denial of service or conduct other unknown impact;
  6. An improper elements handling at V8 can be exploited remotely via a specially designed JavaScript code to cause denial of service or conduct other unknown impact.

Technical details

Vulnerability (2) related to PageCaptureSaveAsMHTMLFunction::ReturnFailure function in browser/extensions/api/page_capture/page_capture_api.cc and can be exploited via triggering error while MHTML document creation.

Vulnerability (3) related to Program::getUniformInternal function in Program.cpp.

Vulnerability (4) related to GetLoadTimes function in renderer/loadtimes_extension_bindings.cc.

Vulnerability (5) related to RenderWidgetHostImpl::Destroy function in content/browser/renderer_host/render_widget_host_impl.cc.

Vulnerability (6) related to Array.prototype.concat implementation in builtins.cc which does not properly consider element data types.

Affected products

Google Chrome versions earlier than 49.0.2623.108

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.
Get Chrome

Original advisories

Google Chrome update blog entry

Impacts
?
ACE 
[?]

DoS 
[?]
Related products
Google Chrome
CVE-IDS
?
CVE-2016-16489.3Critical
CVE-2016-16499.3Critical
CVE-2016-36799.3Critical
CVE-2016-16509.3Critical
CVE-2016-16469.3Critical
CVE-2016-16479.3Critical