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 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 install programs; view, change, or delete data; or create new accounts with full user rights. 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.
- Google Chrome versions prior to 77.0.3865.75
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:
- Arbitrary read in SwiftShader. (CVE-2019-5881)
- Bypass on download restrictions. (CVE-2019-13681)
- Chrome web store origin needs to be isolated. (CVE-2019-13677)
- Cross-origin information leak using devtools. (CVE-2019-13673)
- CSP bypass. (CVE-2019-13662)
- CSRF bypass. (CVE-2019-13664)
- Dialog box fails to show origin. (CVE-2019-13671)
- Download dialog spoofing. (CVE-2019-13678)
- Exceptions leaked by devtools. (CVE-2019-13683)
- Extension can bypass same origin policy. (CVE-2019-5879)
- Extensions can be disabled by trailing slash. (CVE-2019-13675)
- External URIs may trigger other browsers. (CVE-2019-5874)
- Full screen notification overlap. (CVE-2019-13660)
- Full screen notification spoof. (CVE-2019-13661)
- Global window leak via console. (CVE-2019-13668)
- Google URI shown for certificate warning. (CVE-2019-13676)
- Heap overflow in Skia. (CVE-2019-5871)
- HTTP authentication spoof. (CVE-2019-13669)
- IDN spoof. (CVE-2019-13663)
- IDN spoofing. (CVE-2019-13674)
- IP address spoofing to servers. (CVE-2019-13680)
- Multiple file download protection bypass. (CVE-2019-13665)
- Out-of-bounds access in V8. (CVE-2019-5877)
- SameSite cookie bypass. (CVE-2019-5880)
- Side channel using storage size estimate. (CVE-2019-13666)
- Site isolation bypass. (CVE-2019-13682)
- URI bar spoof when using external app URIs. (CVE-2019-13667)
- URL bar spoofing on iOS. (CVE-2019-5873)
- URL bar spoof via download redirect. (CVE-2019-5875)
- URL spoof. (CVE-2019-13659)
- Use-after-free in media. (CVE-2019-5876, CVE-2019-5870)
- Use-after-free in Mojo. (CVE-2019-5872)
- Use-after-free in V8. (CVE-2019-5878)
- User gesture needed for printing. (CVE-2019-13679)
- V8 memory corruption in regex. (CVE-2019-13670)
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.
- 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.
Google:
https://chromereleases.googleblog.com/2019/09/stable-channel-update-for-desktop.html
CVE:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5870
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5871
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5872
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5873
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5874
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5875
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5876
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5877
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5878
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5879
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5880
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5881
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13659
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13660
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13661
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13662
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13663
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13664
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13665
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13666
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13667
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13668
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13669
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13670
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13671
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13673
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13674
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13675
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13676
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13677
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13678
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13679
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13680
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13681
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13682
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13683