Google Chrome 76 releases: improve Dark mode, fix 43 security flaws and more
The Google Chrome development team has now released the first official version of version 76, which brings a number of new features and privacy improvements. For example, malicious websites can use a virtual sandbox to detect whether the user is in incognito mode. For this reason, Google has adjusted the policy to prevent the identification of the website.
In this version, Google Chrome also supports opening and collecting the running log of the extension, but the function should theoretically target professional users. Because the running log is actually the calling record of various interfaces, ordinary users can’t understand the meaning of these records, and naturally can’t check the problem. Interested users can add –enable-extension-activity-logging to manual-open test functionality to Google Chrome launch targets.
Currently, Windows 10 and Google Chrome support dark mode, but the dark mode of Google Chrome is relatively rude. Because the browser’s black mode is just the overall frame and settings turned black, most sites are still light or bright background colors when browsing websites. To this end, Google Chrome also supports the website to read the user’s settings, that is, to detect whether the user is using a light mode or a black mode to make a judgment. Of course, if the website supports dark style, it can automatically switch, but most websites still do not support dark mode to adapt.
Google Chrome 76 includes 43 security fixes.
[$10000][977462] High CVE-2019-5850: Use-after-free in offline page fetcher. Reported by Brendon Tiszka on 2019-06-21
[$6000][956947] High CVE-2019-5860: Use-after-free in PDFium. Reported by Anonymous on 2019-04-26
[$3000][976627] High CVE-2019-5853: Memory corruption in regexp length check. Reported by yngwei(@yngweijw) of IIE Varas and sakura(@eternalsakura13) of Tecent Xuanwu Lab on 2019-06-19
[$3000][977107] High CVE-2019-5851: Use-after-poison in offline audio context. Reported by Zhe Jin(金哲),Luyao Liu(刘路遥) from Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd on 2019-06-20
[$TBD][959438] High CVE-2019-5859: res: URIs can load alternative browsers. Reported by James Lee (@Windowsrcer) of Kryptos Logic on 2019-05-03
[$5000][964245] Medium CVE-2019-5856: Insufficient checks on filesystem: URI permissions. Reported by Yongke Wang of Tencent’s Xuanwu Lab (xlab.tencent.com) on 2019-05-17
[$N/A][943494] Medium CVE-2019-5863: Use-after-free in WebUSB on Windows. Reported by Yuxiang Li (@Xbalien29) of Tencent Security Platform Department on 2019-03-19
[$N/A][964872] Medium CVE-2019-5855: Integer overflow in PDFium. Reported by Zhen Zhou of NSFOCUS Security Team on 2019-05-20
[$TBD][973103] Medium CVE-2019-5865: Site isolation bypass from compromised renderer. Reported by Ivan Fratric of Google Project Zero on 2019-06-11
[$500][960209] Low CVE-2019-5858: Insufficient filtering of Open URL service parameters. Reported by evi1m0 of Bilibili Security Team on 2019-05-07
[$500][936900] Low CVE-2019-5864: Insufficient port filtering in CORS for extensions. Reported by Devin Grindle on 2019-02-28
[$TBD][946260] Low CVE-2019-5862: AppCache not robust to compromised renderers. Reported by Jun Kokatsu, Microsoft Browser Vulnerability Research on 2019-03-26
[$TBD][951525] Low CVE-2019-5861: Click location incorrectly checked. Reported by Robin Linus ( robinlinus.com ) on 2019-04-10
[$N/A][961237] Low CVE-2019-5857: Comparison of -0 and null yields crash. Reported by cloudfuzzer on 2019-05-09
[$N/A][966263] Low CVE-2019-5854: Integer overflow in PDFium text rendering. Reported by Zhen Zhou of NSFOCUS Security Team on 2019-05-23
[$TBD][976713] Low CVE-2019-5852: Object leak of utility functions. Reported by David Erceg on 2019-06-19