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 applications. Depending on the privileges associated with the applications, an attacker could view, change, or delete data. If these applications have been configured to have fewer user rights on the system, exploitation of the most severe of these vulnerabilities could have less impact than if they were configured with administrative rights.

SYSTEMS AFFECTED:

• Google Chrome for Windows versions prior to 102.0.5005.61/62/63
• Google Chrome for Mac and Linux versions prior to 102.0.5005.61

RISK:
‍
Government:

• Large and medium government entities: High
• Small government entities: High

Businesses:

• Large and medium business entities: High
• Small business entities: High

Home users: Low
‍

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

Tactic: Execution (TA0002):

Technique: User Execution (T1204):

• Use after free in Indexed DB (CVE-2022-1853)
• Use after free in ANGLE (CVE-2022-1854)
• Use after free in Messaging (CVE-2022-1855)
• Use after free in User Education (CVE-2022-1856)
• Insufficient policy enforcement in File System API. (CVE-2022-1857)
• Out of bounds read in DevTools. (CVE-2022-1858)
• Use after free in Performance Manager. (CVE-2022-1859)
• Use after free in UI Foundations. (CVE-2022-1860)
• Use after free in Sharing.( CVE-2022-1861)
  ‍

Details of lower-severity vulnerabilities are as follows:

• Inappropriate implementation in Extensions. (CVE-2022-1862)
• Use after free in Tab Groups. (CVE-2022-1863)
• Use after free in WebApp Installs. (CVE-2022-1864)
• Use after free in Bookmarks. (CVE-2022-1865)
• Use after free in Tablet Mode. (CVE-2022-1866)
• Insufficient validation of untrusted input in Data Transfer. (CVE-2022-1867)
• Inappropriate implementation in Extensions API. (CVE-2022-1868)
• Type Confusion in V8. (CVE-2022-1869)
• Use after free in App Service. (CVE-2022-1870)
• Insufficient policy enforcement in File System API. (CVE-2022-1871)
• Insufficient policy enforcement in Extensions API. (CVE-2022-1872)
• Insufficient policy enforcement in COOP. (CVE-2022-1873)
• Insufficient policy enforcement in Safe Browsing. (CVE-2022-1874)
• Inappropriate implementation in PDF. (CVE-2022-1875)
• Heap buffer overflow in DevTools. (CVE-2022-1876)

Successful exploitation of the most severe of these vulnerabilities could allow an attacker to execute arbitrary code in the context of the applications. Depending on the privileges associated with the applications, an attacker could view, change, or delete data. If these applications have been configured to have fewer user rights on the system, exploitation of the most severe of these vulnerabilities could have less impact than if they were configured with administrative rights.

RECOMMENDATIONS:
We recommend the following actions be taken:

1. Apply the stable channel update provided by Google to vulnerable systems     immediately after appropriate testing. (M1051: Update Software)

 
• Safeguard 7.1: Establish and Maintain a Vulnerability Management Process:  Establish and maintain a documented vulnerability management process for      enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
 
• Safeguard  7.4: Perform Automated Application Patch Management: Perform  application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.

2. 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. (M1017: User Training)

 
• Safeguard 14.1: Establish and Maintain a Security Awareness Program: Establish and maintain a security awareness program. The purpose of a security      awareness program is to educate the enterprise’s workforce on how to interact with enterprise assets and data in a secure manner. Conduct training at hire and, at a minimum, annually. Review and update content annually, or when significant enterprise changes occur that could impact this Safeguard.
 
• Safeguard 14.2: Train Workforce Members to Recognize Social Engineering Attacks: Train workforce members to recognize social engineering attacks, such as phishing, pre-texting, and tailgating.

3. Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account  Management)

 
• Safeguard 4.7: Manage Default Accounts on  Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root,      administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
 
• Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.

4. Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040 : Behavior Prevention on Endpoint)

 
• Safeguard 13.2 : Deploy a Host-Based Intrusion Detection  Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.

Safeguard 13.7: Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

REFERENCES:

Google:​​​​​​https://chromereleases.googleblog.com/

CVE:​​​​​https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1853

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1854

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1855

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1856

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1857

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1858

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1859

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1860

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1861

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1862

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1863

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1864

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1865

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1866

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1867

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1868

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1869

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1870

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1871

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1872

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1873

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1874

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1875

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1876

‍