Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

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 for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

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

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:
Tactic: Initial Access (TA0002):
Technique: Drive -by Compromise (T1189):

• Use after free in Omnibox. (CVE-2022-2603)
• Use after free in Safe Browsing. (CVE-2022-2604)
• Out of bounds read in Dawn. (CVE-2022-2605)
• Use after free in Managed devices API. (CVE-2022-2606)
• Use after free in Tab Strip. (CVE-2022-2607)
• Use after free in Overview Mode. (CVE-2022-2608)
• Use after free in Nearby Share. (CVE-2022-2609)
  Details of lower-severity vulnerabilities are as follows:
• Insufficient policy enforcement in Background Fetch. (CVE-2022-2610)
• Inappropriate implementation in Fullscreen API. (CVE-2022-2611)
• Side-channel information leakage in Keyboard input. (CVE-2022-2612)
• Use after free in Input. (CVE-2022-2613)
• Use after free in Sign-In Flow. (CVE-2022-2614)
• Insufficient policy enforcement in Cookies. (CVE-2022-2615)
• Inappropriate implementation in Extensions API. (CVE-2022-2616)
• Use after free in Extensions API. (CVE-2022-2617)
• Insufficient validation of untrusted input in Internals. (CVE-2022-2618)
• Insufficient validation of untrusted input in Settings. (CVE-2022-2619)
• Use after free in WebUI. (CVE-2022-2620)
• Use after free in Extensions. (CVE-2022-2621)
• Insufficient validation of untrusted input in Safe Browsing. (CVE-2022-2622)
• Use after free in Offline. (CVE-2022-2623)
• Heap buffer overflow in PDF. (CVE-2022-2624)
  Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

We recommend the following actions be taken:

• Apply the stable channel update provided by Google to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
  o 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.
  o 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.
• 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)
  o 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.
  o 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.
• Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
  o Safeguard 9.2: Use DNS Filtering Services: Use DNS filtering services on all enterprise assets to block access to known malicious domains.
  o Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
• Train users to be aware of access or manipulation attempts by an adversary to reduce the risk of successful spearphishing, social engineering, and other techniques that involve user interaction. (M1017: User Training)
  o 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.
  o Safeguard 14.6: Train Workforce Members on Recognizing and Reporting Security Incidents: Train workforce members to be able to recognize a potential incident and be able to report such an incident.
  REFERENCES: