Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

ITS Advisory Number: 
2018-025
Date(s) Issued: 
Wednesday, March 7, 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 65.0.3325.146

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 Flash. (CVE-2018-6058, CVE-2018-6059)

  • Incorrect permissions on shared memory. (CVE-2018-6057, CVE-2018-6063)

  • Use after free in Blink. (CVE-2018-6060)

  • Race condition in V8. (CVE-2018-6061)

  • Heap buffer overflow in Skia. (CVE-2018-6062)

  • Incorrect permissions on shared memory. (CVE-2018-6057, CVE-2018-6063)

  • Type confusion in V8. (CVE-2018-6064)

  • Integer overflow in V8. (CVE-2018-6065)

  • Same Origin Bypass via canvas. (CVE-2018-6066)

  • Buffer overflow in Skia. (CVE-2018-6067)

  • Object lifecycle issues in Chrome Custom Tab. (CVE-2018-6068)

  • Stack buffer overflow in Skia. (CVE-2018-6069)

  • CSP bypass through extensions. (CVE-2018-6070)

  • Heap bufffer overflow in Skia. (CVE-2018-6071)

  • Integer overflow in PDFium. (CVE-2018-6072)

  • Heap bufffer overflow in WebGL. (CVE-2018-6073)

  • Mark-of-the-Web bypass. (CVE-2018-6074)

  • Overly permissive cross origin downloads. (CVE-2018-6075)

  • Incorrect handling of URL fragment identifiers in Blink. (CVE-2018-6076)

  • Timing attack using SVG filters. (CVE-2018-6077)

  • URL Spoof in OmniBox. (CVE-2018-6078)

  • Information disclosure via texture data in WebGL. (CVE-2018-6079)

  • Information disclosure in IPC call. (CVE-2018-6080)

  • XSS in interstitials. (CVE-2018-6081)

  • Circumvention of port blocking. (CVE-2018-6082)

  • Incorrect processing of AppManifests. (CVE-2018-6083)

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/03/stable-channel-update-for-desktop.html

 

CVE: 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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