Multiple Vulnerabilities in Google Chrome Could Allow for Code Execution

ITS Advisory Number: 
2016-203
Date(s) Issued: 
Friday, December 2, 2016
Subject: 
Multiple Vulnerabilities in Google Chrome Could Allow for Code Execution
Overview: 

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could result in code execution. Google Chrome is a web browser used to access the Internet. These vulnerabilities can be exploited if a user visits, or is redirected to, a specially crafted web page. Successful exploitation of these vulnerabilities could allow an attacker to execute code in the context of the browser, obtain sensitive information, bypass security restrictions, or cause denial-of-service conditions.

 

Systems Affected: 
  • Google Chrome prior to 55.0.2883.75
RISK
GOVERNMENT
Large and medium government entities: 
High
Small government entities: 
Medium
BUSINESS
Large and medium business entities: 
High
Small business entities: 
Medium
Home Users: 
Low
Description: 

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could result in remote code execution. These vulnerabilities can be exploited if a user visits, or is redirected to, a specially crafted web page. Details of the vulnerabilities are as follows:

  • Private property access in V8 (CVE-2016-9651)
  • Universal XSS in Blink (CVE-2016-5208, CVE-2016-5207, CVE-2016-5205, CVE-2016-5204)
  • Same-origin bypass in PDFium (CVE-2016-5206)
  • Out of bounds write in Blink (CVE-2016-5209)
  • Use after free in PDFium (CVE-2016-5203, CVE-2016-5211, CVE-2016-5216)
  • Out of bounds write in PDFium (CVE-2016-5210)
  • Local file disclosure in DevTools (CVE-2016-5212)
  • Use after free in V8 (CVE-2016-5213, CVE-2016-5219)
  • File download protection bypass (CVE-2016-5214)
  • Use after free in Webaudio (CVE-2016-5215)
  • Use of unvalidated data in PDFium (CVE-2016-5217)
  • Address spoofing in Omnibox (CVE-2016-5218, CVE-2016-5222)
  • Integer overflow in ANGLE (CVE-2016-5221)
  • Local file access in PDFium (CVE-2016-5220)
  • CSP Referrer disclosure (CVE-2016-9650)
  • Integer overflow in PDFium (CVE-2016-5223)
  • Limited XSS in Blink (CVE-2016-5226)
  • CSP bypass in Blink (CVE-2016-5225)
  • Same-origin bypass in SVG (CVE-2016-5224)
  • Various fixes from internal audits, fuzzing and other initiatives (CVE-2016-9652)

Successful exploitation of these vulnerabilities could allow an attacker to execute remote code in the context of the browser, obtain sensitive information, bypass security restrictions, or cause denial-of-service conditions.

Actions: 
  • After appropriate testing, apply patches provided by Google to vulnerable systems.

  • Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack.

  • Remind users not to visit un-trusted websites or follow links provided by unknown or un-trusted sources.

  • Inform and educate users regarding the threats posed by hypertext links contained in emails or attachments especially from un-trusted sources.

  • Apply the Principle of Least Privilege to all systems and services.

References: 

Google:

https://googlechromereleases.blogspot.com/2016/12/stable-channel-update-for-desktop.html

 

CVE:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5203

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5204

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5205

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5206

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5207

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5208

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5209

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5210

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5211

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5212

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5213

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5214

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5215

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5216

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5217

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5218

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5219

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5220

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5221

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5222

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5223

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5224

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5225

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5226

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9650

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9651

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9652