Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

ITS Advisory Number: 
2018-060
Date(s) Issued: 
Wednesday, May 30, 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.

THREAT INTELLIGENCE:

There are currently no reports of these vulnerabilities being exploited in the wild.

Systems Affected: 
  • Google Chrome prior to 67.0.3396.62
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 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:

  • Heap buffer overflow in Skia. (CVE-2018-6141, CVE-2018-6126)
  • Incorrect escaping of MathML in Blink. (CVE-2018-6145)
  • Incorrect mutability protection in WebAssembly. (CVE-2018-6131)
  • Leak of visited status of page in Blink. (CVE-2018-6137)
  • Out of bounds memory access in PDFium. (CVE-2018-6144)
  • Out of bounds memory access in V8. (CVE-2018-6136, CVE-2018-6142, CVE-2018-6143)
  • Out of bounds memory access in WebRTC. (CVE-2018-6130, CVE-2018-6129)
  • Overly permissive policy in Extensions. (CVE-2018-6138)
  • Overly permissive policy in WebUSB. (CVE-2018-6125)
  • Password fields not taking advantage of OS protections in Views. (CVE-2018-6147)
  • Referrer Policy bypass in Blink. (CVE-2018-6134)
  • Restrictions bypass in the debugger extension API. (CVE-2018-6140, CVE-2018-6139)
  • Type confusion in Blink. (CVE-2018-6124)
  • UI spoofing in Blink. (CVE-2018-6135)
  • URL spoof in Omnibox. (CVE-2018-6133)
  • Use after free in Blink. (CVE-2018-6123)
  • Use after free in indexedDB. (CVE-2018-6127)
  • Use of uninitialized memory in WebRTC. (CVE-2018-6132)
  • uXSS in Chrome on iOS. (CVE-2018-6128)

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 the 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/05/stable-channel-update-for-desktop_58.html

CVE: 

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6123

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6124

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6125

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6126

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6127

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6128

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6129

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6130

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6131

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6132

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6133

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6134

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6135

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6136

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6137

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6138

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6139

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6140

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6141

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6142

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6143

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6144

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6145

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6147