Multiple Vulnerabilities in Google Chrome Could Allow for Arbitrary Code Execution

MS-ISAC ADVISORY NUMBER:

DATE(S) ISSUED:

OVERVIEW:

Multiple vulnerabilities have been discovered in Google Chrome, the most severe of which could result in arbitrary code execution. Google Chrome is a web browser used to access the Internet. These vulnerabilities can be exploited if a user visits, or is redirected to, a specially crafted web page. Successful exploitation of the most severe of these vulnerabilities could allow an attacker to execute arbitrary code in the context of the browser, obtain sensitive information, bypass security restrictions and perform unauthorized actions, or cause denial-of-service conditions.

THREAT INTELLIGENCE:

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

As of this release, Google Chrome will show a “Not secure” designation on any website running Hyper Text Transfer Protocol (HTTP) instead of Hyper Text Transfer Protocol Secure (HTTPS), which may give users the perception that a state, local, tribal, or territorial (SLTT) government website is unsecure. The MS-ISAC recommends members follow federal guidelines, such as those outlined in OMB Memorandum M-15-13 and on the OMB HTTPS-Only Standard website. Additional information is also available in the EI-ISAC Cybersecurity Spotlight “Hyper Text Transfer Protocol Secure (HTTPS)” and the MS-ISAC White Paper “White House Announces Federal Websites Must Move to HTTPS.”

SYSTEMS AFFECTED:

• Google Chrome prior to 68.0.3440.75

RISK:

TECHNICAL SUMMARY:

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

• CORS bypass in Blink (CVE-2018-6168)
• Cross origin information leak in Blink (CVE-2018-4117, CVE-2018-6177)
• Heap buffer overflow in WebGL (CVE-2018-6154, CVE-2018-6162)
• Heap buffer overflow in WebRTC (CVE-2018-6156)
• Integer overflow in SwiftShader (CVE-2018-6174)
• Local file information leak in Extensions (CVE-2018-6179)
• Local user privilege escalation in Extensions (CVE-2018-6176)
• Permissions bypass in extension installation (CVE-2018-6169)
• Request privilege escalation in Extensions (CVE-2018-6044)
• Same origin policy bypass in ServiceWorker (CVE-2018-6159, CVE-2018-6164)
• Same origin policy bypass in WebAudio (CVE-2018-6161)
• Stack buffer overflow in Skia (CVE-2018-6153)
• Type confusion in PDFium (CVE-2018-6170)
• Type confusion in WebRTC (CVE-2018-6157)
• UI spoof in Extensions (CVE-2018-6178)
• URL spoof in Chrome on iOS (CVE-2018-6160)
• URL spoof in Omnibox (CVE-2018-6163, CVE-2018-6165, CVE-2018-6166, CVE-2018-6167, CVE-2018-6172, CVE-2018-6173, CVE-2018-6175)
• Use after free in Blink (CVE-2018-6158)
• Use after free in WebBluetooth (CVE-2018-6171)
• Use after free in WebRTC (CVE-2018-6155)

Successful exploitation of the most severe of these vulnerabilities could allow an attacker to execute arbitrary code in the context of the browser, obtain sensitive information, bypass security restrictions and perform unauthorized actions, or cause denial-of-service conditions.

RECOMENDATIONS:

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: