Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

ITS Advisory Number: 
2018-044
Date(s) Issued: 
Thursday, April 19, 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 66.0.3359.117
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 these vulnerabilities are as follows:

  • Use after free in Disk Cache (CVE-2018-6085, CVE-2018-6086).
  • Use after free in WebAssembly (CVE-2018-6087).
  • Use after free in PDFium (CVE-2018-6088).
  • Same origin policy bypass in Service Worker (CVE-2018-6089).
  • Heap buffer overflow in Skia (CVE-2018-6090).
  • Incorrect handling of plug-ins by Service Worker (CVE-2018-6091).
  • Integer overflow in WebAssembly (CVE-2018-6092).
  • Same origin bypass in Service Worker (CVE-2018-6093).
  • Exploit hardening regression in Oilpan (CVE-2018-6094).
  • Lack of meaningful user interaction requirement before file upload (CVE-2018-6095).
  • Fullscreen UI spoof (CVE-2018-6096, CVE-2018-6097).
  • URL spoof in Omnibox (CVE-2018-6098, CVE-2018-6100, CVE-2018-6102, CVE-2018-6104, CVE-2018-6105, CVE-2018-6107, CVE-2018-6108).
  • CORS bypass in ServiceWorker (CVE-2018-6099).
  • Insufficient protection of remote debugging prototol in DevTools  (CVE-2018-6101).
  • UI spoof in Permissions (CVE-2018-6103).
  • Incorrect handling of promises in V8 (CVE-2018-6106).
  • Incorrect handling of files by FileAPI (CVE-2018-6109).
  • Incorrect handling of plaintext files via file (CVE-2018-6110).
  • Heap-use-after-free in DevTools (CVE-2018-6111).
  • Incorrect URL handling in DevTools (CVE-2018-6112).
  • URL spoof in Navigation (CVE-2018-6113).
  • CSP bypass (CVE-2018-6114).
  • SmartScreen bypass in downloads (CVE-2018-6115).
  • Incorrect memory handling in WebAssembly (CVE-2018-6116).
  • Confusing autofill settings (CVE-2018-6117).
  • Incorrect use of Distributed Objects in Google Software Updater on MacOS (CVE-2018-6084).

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 immediately after appropriate testing.
  • 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/04/stable-channel-update-for-desktop.html

CVE: 

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6084

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6085

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6086

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6087

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6088

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6089

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6090

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6091

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6092

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6093

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6094

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6095

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6096

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6097

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6098

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6099

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6100

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6101

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6102

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6103

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6104

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6105

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6106

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6107

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6108

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6109

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6110

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6111

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6112

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6113

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6114

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-611

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6116

">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6117