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

Multiple serious vulnerabilities have been found in Google Chrome. Malicious users can exploit these vulnerabilities to spoof user interface, cause denial of service, bypass security restrictions or conduct another unknown impact.

Below is a complete list of vulnerabilities

  1. Lack of restrictions at Blink can be exploited remotely via a specially designed JavaScript to bypass security restrictions;
  2. An improper parameters handling at Development Tools can be exploited remotely via a specially designed URL to bypass security restrictions;
  3. An improper data buffers handling at Blink can be exploited remotely via a specially designed JavaScript to cause denial of service or conduct another unspecified impact;
  4. An unknown vulnerability can be exploited remotely via a specially designed URL to spoof user interface;
  5. Buffer overflow at PDFium can be exploited remotely via a specially designed JPEG2000 data to cause denial of service or conduct another unknown impact.

Technical details

Vulnerability №1 caused by a taint property which is preserved after a structure-clone operation on an ImageBitmap object derived from a cross-origin image.

Vulnerability №2 caused by mishandling the script-path hostname, remoteBase parameter, and remoteFrontendUrl parameter.

Vulnerability №3 caused by improper copying data buffers

Vulnerability №4 can be exploited via vectors involving a provisional URL for an initially empty document and related to FrameLoader.cpp and ScopedPageLoadDeferrer.cpp

Vulnerability №5 caused by Heap-based buffer overflow in the opj_j2k_read_SQcd_SQcc function in j2k.c in OpenJPEG

Affected products

Google Chrome verions earlier than 52.0.2743.116 (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.
Get Google Chrome

Original advisories

Google Chrome releases blog

Impacts
?
DoS 
[?]

SB 
[?]

SUI 
[?]
Related products
Google Chrome
CVE-IDS
?
CVE-2016-51467.5Critical
CVE-2016-51456.8High
CVE-2016-51447.5Critical
CVE-2016-51437.5Critical
CVE-2016-51427.5Critical
CVE-2016-51415.0Critical
CVE-2016-51407.5Critical