Multiple serious vulnerabilities have been found in Google Chrome. Malicious users can exploit these vulnerabilities to cause denial of service, obtain sensitive information, spoof user interface, bypass security restrictions and possibly to execute arbitrary code.

Below is a complete list of vulnerabilities:

1. Out of bounds write in QUIC can be exploited remotely possibly to bypass security restrictions;
2. Heap buffer overflow in PDFium can be exploited remotely possibly to execute arbitrary code;
3. Out of bounds write in Skia can be exploited remotely possibly to execute arbitrary code;
4. Use after free in PDFium can be exploited remotely possibly to execute arbitrary code;
5. Use after free in libXML can be exploited remotely possibly to execute arbitrary code;
6. Type confusion in WebAssembly can be exploited remotely possibly to bypass security restrictions, execute arbitrary code and obtain sensitive information;
7. Pointer information disclosure in IPC call can be exploited remotely possibly to obtain sensitive information;
8. Out of bounds read in Blink can be exploited remotely possibly to obtain sensitive information;
9. Cross origin information disclosure in Skia can be exploited remotely possibly to obtain sensitive information;
10. Use of uninitialized value in Skia can be exploited remotely possibly to bypass security restrictions and disclose sensitive information;
11. Cross origin leak of redirect URL in Blink can be exploited remotely possibly to obtain sensitive information;
12. URL spoofing in Omniboxcan can be exploited remotely possibly to spoof user interface;
13. Integer overflow in ICU can be exploited remotely possibly to cause denial of service;
14. Issue with SPAKE implementation in BoringSSL can be exploited remotely possibly to obtain sensitive information;
15. Insufficient blocking of JavaScript in Omnibox can be exploited remotely possibly to perform a cross-site scripting (XSS) attack;

Technical details

NB: At this moment Google has just reserved CVE numbers for these vulnerabilities. Information can be changed soon.

Google Chrome versions earlier than 63.0.3239.84

Update to the latest version. File with name old_chrome can be still detected after update. It caused by Google Chrome update policy which does not remove old versions when installing updates. Try to contact vendor for further delete instructions or ignore such kind of alerts at your own risk.
Download Google Chrome

Stable Channel Update for Desktop