Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

ITS Advisory Number: 
2022-001
Date(s) Issued: 
Wednesday, January 5, 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 no reports that these vulnerabilities are being exploited in the wild.

 

Systems Affected: 
  • Google Chrome version 97.0.4692.71
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 allow for arbitrary code execution. Details of the vulnerabilities are as follows:

 

  • Use after free in Storage. (CVE-2022-0096)
  • Inappropriate implementation in DevTools. (CVE-2022-0097)
  • Use after free in Screen Capture. (CVE-2022-0098)
  • Use after free in Sign-in. (CVE-2022-0099)
  • Heap buffer overflow in Media streams API. (CVE-2022-0100)
  • Heap buffer overflow in Bookmarks. (CVE-2022-0101)
  • Type Confusion in V8. (CVE-2022-0102)
  • Use after free in SwiftShader. (CVE-2022-0103)
  • Heap buffer overflow in ANGLE. (CVE-2022-0104)
  • Use after free in PDF. (CVE-2022-0105)
  • Use after free in Autofill. (CVE-2022-0106)
  • Use after free in File Manager API. (CVE-2022-0107)
  • Inappropriate implementation in Navigation. (CVE-2022-0108)
  • Inappropriate implementation in Autofill. (CVE-2022-0109)
  • Incorrect security UI in Autofill. (CVE-2022-0110)
  • Inappropriate implementation in Navigation. (CVE-2022-0111)
  • Incorrect security UI in Browser UI. (CVE-2022-0112)
  • Inappropriate implementation in Blink. (CVE-2022-0113)
  • Out of bounds memory access in Web Serial. (CVE-2022-0114)
  • Uninitialized Use in File API. (CVE-2022-0115)
  • Inappropriate implementation in Compositing. (CVE-2022-0116)
  • Policy bypass in Service Workers. (CVE-2022-0117)
  • Inappropriate implementation in WebShare. (CVE-2022-0118)
  • Inappropriate implementation in Passwords. (CVE-2022-0120)

 

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: 
  • 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/2022/01/stable-channel-update-for-...

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0096
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0097
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0098
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0099
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0100
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0101
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0102
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0103
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0104
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0105
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0106
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0107
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0108
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0109
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0110
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0111
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0112
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0113
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0114
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0115
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0116
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0117
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0118
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0120