Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

ITS Advisory Number: 
2020-095
Date(s) Issued: 
Wednesday, July 15, 2020
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. Successful exploitation of the most severe of these vulnerabilities could allow an attacker to execute arbitrary code in the context of the browser. Depending on the privileges associated with the application, an attacker could install programs; view, change, or delete data; or create new accounts with full user rights. If this application has been configured to have fewer user rights on the system, exploitation of the most severe of these vulnerabilities could have less impact than if it was configured with administrative rights.

 

THREAT INTELLIGENCE:

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

Systems Affected: 
  • Google Chrome versions prior to 84.0.4147.89

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. Details of these vulnerabilities are as follows: 

  • Heap buffer overflow in background fetch. (CVE-2020-6510)

  • Heap buffer overflow in history. (CVE-2020-6517)

  • Heap buffer overflow in PDFium. (CVE-2020-6513)

  • Heap buffer overflow in Skia. (CVE-2020-6520, CVE-2020-6525)

  • Heap buffer overflow in WebAudio. (CVE-2020-6524)

  • Heap buffer overflow in WebRTC. (CVE-2020-6534)

  • Inappropriate implementation in external protocol handlers. (CVE-2020-6522)

  • Inappropriate implementation in iframe sandbox. (CVE-2020-6526)

  • Inappropriate implementation in WebRTC. (CVE-2020-6529, CVE-2020-6514)

  • Incorrect security UI in basic auth. (CVE-2020-6528)

  • Incorrect security UI in PWAs. (CVE-2020-6536)

  • Insufficient data validation in WebUI. (CVE-2020-6535)

  • Insufficient policy enforcement in CSP. (CVE-2020-6527)

  • Out of bounds memory access in developer tools. (CVE-2020-6530)

  • Out of bounds write in Skia. (CVE-2020-6523)

  • Policy bypass in CORS. (CVE-2020-6516)

  • Policy bypass in CSP. (CVE-2020-6519)

  • Side-channel information leakage in autofill. (CVE-2020-6521)

  • Side-channel information leakage in content security policy. (CVE-2020-6511)

  • Side-channel information leakage in scroll to text. (CVE-2020-6531)

  • Type Confusion in V8. (CVE-2020-6512, CVE-2020-6533)

  • Use after free in developer tools. (CVE-2020-6518)

  • Use after free in tab strip. (CVE-2020-6515) 

Successful exploitation of the most severe of these vulnerabilities could allow an attacker to execute arbitrary code in the context of the browser. Depending on the privileges associated with the application, an attacker could install programs; view, change, or delete data; or create new accounts with full user rights. If this application has been configured to have fewer user rights on the system, exploitation of the most severe of these vulnerabilities could have less impact than if it was configured with administrative rights.

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/2020/07/stable-channel-update-for-...

CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6510
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6511
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6512
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6513
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6514
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6515
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6516
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6517
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6518
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6519
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6520
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6521
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6522
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6523
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6524
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6525
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6526
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6527
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6528
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6529
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6530
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6531
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6533
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6534
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6535
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6536