Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

Summary

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could allow for arbitrary code execution. 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 81.0.4044.92

Risk

Government

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

Businesses

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

Home Users: Low

Technical Details

These vulnerabilities can be exploited if a user visits, or is redirected to, a specially crafted web page. Details of the vulnerabilities are as follows:

• Use-after-free vulnerability in the WebAudio component. (CVE-2020-6423)
• Type-confusion vulnerability in the V8 component. (CVE-2020-6430)
• Insufficient-policy-enforcement vulnerability the Full-Screen component. (CVE-2020-6431)
• Insufficient-policy-enforcement vulnerability the Navigations component. (CVE-2020-6432)
• Insufficient-policy-enforcement vulnerability the Extensions component. (CVE-2020-6433)
• Use-after-free vulnerability the Devtools component. (CVE-2020-6434)
• Insufficient-policy-enforcement vulnerability the Devtools component. (CVE-2020-6435)
• Use-after-free vulnerability in the Windows-Management component. (CVE-2020-6436)
• Inappropriate-implementation vulnerability the WebView component. (CVE-2020-6437)
• Insufficient-policy-enforcement vulnerability the Extensions component. (CVE-2020-6438)
• Insufficient-policy-enforcement vulnerability the Navigations component. (CVE-2020-6439)
• Inappropriate-implementation vulnerability the Extensions component. (CVE-2020-6440)
• Insufficient-policy-enforcement vulnerability the Omnibox component. (CVE-2020-6441)
• Inappropriate-implementation vulnerability the Cache component. (CVE-2020-6442)
• Insufficient-data-validation the Devtools component. (CVE-2020-6443)
• Uninitialized memory use issue in the WebRTC component. (CVE-2020-6444)
• Insufficient-policy-enforcement vulnerability the Trusted-types component. (CVE-2020-6445)
• Insufficient-policy-enforcement vulnerability the Trusted-types component. (CVE-2020-6446)
• Inappropriate-implementation vulnerability the Devtools component. (CVE-2020-6447)
• Use-after-free vulnerability in the V8 component. (CVE-2020-6448)
• Use-after-free vulnerability the Extensions component. (CVE-2020-6454)
• Out-of-bounds read vulnerability in the Media component. (CVE-2020-6455)
• Insufficient-validation-of-untrusted-input vulnerability in the Clipboard component. (CVE-2020-6456)

Recommendations

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

CVE:

• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6423
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6430
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6431
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6432
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6433
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6434
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6435
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6436
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6437
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6438
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6439
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6440
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6441
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6442
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6443
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6444
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6445
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6446
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6447
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6448
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6454
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6455
• http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6456

Reporting

The NJCCIC encourages recipients who discover signs of malicious cyber activity to contact the NJCCIC via the cyber incident report form by clicking here.

Please do not hesitate to contact the NJCCIC at njccic@cyber.nj.gov with any questions.