Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

ITS Advisory Number: 
2018-010
Date(s) Issued: 
Thursday, January 25, 2018
Subject: 
Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution
Overview: 

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could result in arbitrary 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 the most severe of these vulnerabilities could allow an attacker to execute arbitrary code in the context of the browser, obtain sensitive information, bypass security restrictions and perform unauthorized actions, or cause denial-of-service conditions.

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

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could result in arbitrary 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:

 

  • Use after free in PDFium. (CVE-2018-6031)
  • Same origin bypass in Shared Worker. (CVE-2018-6032)
  • Race when opening downloaded files. (CVE-2018-6033)
  • Integer overflow in Blink. (CVE-2018-6034)
  • Insufficient isolation of devtools from extensions. (CVE-2018-6035, CVE-2018-6045, CVE-2018-6046)
  • Integer underflow in WebAssembly. (CVE-2018-6036)
  • Insufficient user gesture requirements in autofill. (CVE-2018-6037)
  • Heap buffer overflow in WebGL. (CVE-2018-6038)
  • XSS in DevTools. (CVE-2018-6039)
  • Content security policy bypass. (CVE-2018-6040)
  • URL spoof in Navigation. (CVE-2018-6041)
  • URL spoof in OmniBox. (CVE-2018-6042, CVE-2018-6050)
  • Insufficient escaping with external URL handlers. (CVE-2018-6043)
  • Cross origin URL leak in WebGL. (CVE-2018-6047)
  • Referrer policy bypass in Blink. (CVE-2018-6048)
  • URL spoofing in Omnibox. (CVE-2017-15420)
  • UI spoof in Permissions. (CVE-2018-6049)
  • Referrer leak in XSS Auditor. (CVE-2018-6051)
  • Incomplete no-referrer policy implementation. (CVE-2018-6052)
  • Leak of page thumbnails in New Tab Page. (CVE-2018-6053)
  • Use after free in WebUI. (CVE-2018-6054)

 

Successful exploitation of the most severe of these vulnerabilities could allow an attacker to execute arbitrary code in the context of the browser, obtain sensitive information, bypass security restrictions and perform unauthorized actions, or cause denial-of-service conditions.

Actions: 
  • After appropriate testing, immediately apply stable channel update 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://chromereleases.googleblog.com/2018/01/stable-channel-update-for-...

CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15420
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6031
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6032
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6033
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6034
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6035
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6036
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6037
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6038
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6039
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6040
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6041
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6042
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6043
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6045
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6046
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6047
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6048
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6049
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6050
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6051
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6052
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6053
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6054