Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

ITS Advisory Number: 
2022-059
Date(s) Issued: 
Wednesday, April 27, 2022
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 allow for 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 view, change, or delete data. 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 101.0.4951.41

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: 
Low
Description: 

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could allow for arbitrary code execution. Details of the vulnerabilities are as follows:

  • CVE-2022-1477: Use after free in Vulkan

  • CVE-2022-1478: Use after free in SwiftShader

  • CVE-2022-1479: Use after free in ANGLE

  • CVE-2022-1480: Use after free in Device API

  • CVE-2022-1481: Use after free in Sharing

  • CVE-2022-1482: Inappropriate implementation in WebGL

  • CVE-2022-1483: Heap buffer overflow in WebGPU

  • CVE-2022-1484: Heap buffer overflow in Web UI Settings

  • CVE-2022-1485: Use after free in File System API

  • CVE-2022-1486: Type Confusion in V8

  • CVE-2022-1487: Use after free in Ozone

  • CVE-2022-1488: Inappropriate implementation in Extensions API

  • CVE-2022-1489: Out of bounds memory access in UI Shelf

  • CVE-2022-1490: Use after free in Browser Switcher

  • CVE-2022-1491: Use after free in Bookmarks

  • CVE-2022-1492: Insufficient data validation in Blink Editing

  • CVE-2022-1493: Use after free in Dev Tools

  • CVE-2022-1494: Insufficient data validation in Trusted Types

  • CVE-2022-1495: Incorrect security UI in Downloads

  • CVE-2022-1496: Use after free in File Manager

  • CVE-2022-1497: Inappropriate implementation in Input

  • CVE-2022-1498: Inappropriate implementation in HTML Parser

  • CVE-2022-1499: Inappropriate implementation in WebAuthentication

  • CVE-2022-1500: Insufficient data validation in Dev Tools

  • CVE-2022-1501: Inappropriate implementation in iframe

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 view, change, or delete data. 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: 

We recommend the following actions be taken:

  • Apply the 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/2022/04/stable-channel-update-for-...

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1477
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1478
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1479
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1480
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1481
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1482
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1483
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1484
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1485
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1486
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1487
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1488
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1489
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1490
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1491
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1492
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1493
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1494
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1495
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1496
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1497
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1498
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1499
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1500
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1501