Chrome 66 Is Out: Autoplay Content Restrictions, Site Isolation (Spectre), Password Export, and Fixes for 62 Security Issues

Author Photo
Apr 18, 2018
16Shares
Submit

Google has started to release Chrome 66 for Windows, Android, iOS, Mac, and Linux. The latest browser version brings several features, policy changes, and security improvements. Some of the highlights include:

  • New media autoplay behavior: autoplaying content is muted by default along with other restrictions/permissions
  • Passwords export feature: You can download .csv file in “Managed passwords” download chrome 66
  • Site Isolation Trial: improves security and helps mitigate the risks posed by Spectre chip bug by running pages from different websites in different processes with each process blocked from receiving sensitive data from other sites
  • Chrome will no longer trust Symantec‘s legacy PKI
  • Over 62 security fixes

Back in January, Google allowed Chrome users to mute audio on a site-by-site basis with Chrome 64. Adding on to that experience, Chrome 66 will now automatically mute content unless the user has frequently played media on the site based Media Engagement Index, or a site has been added to the Home Screen on mobile.

andy-rubin-googleRelated Sundar Pichai Supports Engineers’ Women’s Walk Tomorrow Protesting Company’s Mishandling of Sexual Misconduct – Another Exec Leaves

Chrome 66 addresses 62 security flaws

Today’s release also brings fixes to several security issues. The company said that “access to bug details and links may be kept restricted until a majority of users are updated with a fix.” Here’s the complete changelog of all the security issues that Chrome 66 is fixing, including several bugs rated critical or high in severity:

  • Critical CVE-2018-6085: Use after free in Disk Cache. Reported by Ned Williamson on 2018-03-28
  • Critical CVE-2018-6086: Use after free in Disk Cache. Reported by Ned Williamson on 2018-03-30
  • High CVE-2018-6087: Use after free in WebAssembly. Reported by Anonymous on 2018-02-20
  • High CVE-2018-6088: Use after free in PDFium. Reported by Anonymous on 2018-03-15
  • High CVE-2018-6089: Same origin policy bypass in Service Worker. Reported by Rob Wu on 2018-02-04
  • High CVE-2018-6090: Heap buffer overflow in Skia. Reported by ZhanJia Song on 2018-03-12
  • High CVE-2018-6091: Incorrect handling of plug-ins by Service Worker. Reported by Jun Kokatsu (@shhnjk) on 2017-10-05
  • High CVE-2018-6092: Integer overflow in WebAssembly. Reported by Natalie Silvanovich of Google Project Zero on 2018-03-08
  • Medium CVE-2018-6093: Same origin bypass in Service Worker. Reported by Jun Kokatsu (@shhnjk) on 2017-11-01
  • Medium CVE-2018-6094: Exploit hardening regression in Oilpan. Reported by Chris Rohlf on 2016-08-01
  • Medium CVE-2018-6095: Lack of meaningful user interaction requirement before file upload. Reported by Abdulrahman Alqabandi (@qab) on 2016-08-11
  • Medium CVE-2018-6096: Fullscreen UI spoof. Reported by WenXu Wu of Tencent’s Xuanwu Lab on 2017-10-19
  • Medium CVE-2018-6097: Fullscreen UI spoof. Reported by xisigr of Tencent’s Xuanwu Lab on 2018-01-26
  • Medium CVE-2018-6098: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-01-03
  • Medium CVE-2018-6099: CORS bypass in ServiceWorker. Reported by Jun Kokatsu (@shhnjk) on 2018-02-03
  • Medium CVE-2018-6100: URL spoof in Omnibox. Reported by Lnyas Zhang on 2018-02-11
  • Medium CVE-2018-6101: Insufficient protection of remote debugging prototol in DevTools . Reported by Rob Wu on 2018-02-19
  • Medium CVE-2018-6102: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-02-20
  • Medium CVE-2018-6103: UI spoof in Permissions. Reported by Khalil Zhani on 2018-02-24
  • Medium CVE-2018-6104: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-03-08
  • Medium CVE-2018-6105: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-01-18
  • Medium CVE-2018-6106: Incorrect handling of promises in V8. Reported by lokihardt of Google Project Zero on 2018-01-25
  • Medium CVE-2018-6107: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-02-02
  • Medium CVE-2018-6108: URL spoof in Omnibox. Reported by Khalil Zhani on 2018-02-27
  • Low CVE-2018-6109: Incorrect handling of files by FileAPI. Reported by Dominik Weber (@DoWeb_) on 2017-04-10
  • Low CVE-2018-6110: Incorrect handling of plaintext files via file:// . Reported by Wenxiang Qian (aka blastxiang) on 2017-10-24
  • Low CVE-2018-6111: Heap-use-after-free in DevTools. Reported by Khalil Zhani on 2017-11-02
  • Low CVE-2018-6112: Incorrect URL handling in DevTools. Reported by Rob Wu on 2017-12-29
  • Low CVE-2018-6113: URL spoof in Navigation. Reported by Khalil Zhani on 2018-01-25
  • Low CVE-2018-6114: CSP bypass. Reported by Lnyas Zhang on 2018-02-13
  • Low CVE-2018-6115: SmartScreen bypass in downloads. Reported by James Feher on 2018-03-07
  • Low CVE-2018-6116: Incorrect low memory handling in WebAssembly. Reported by Jin from Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd. on 2018-03-15
  • Low CVE-2018-6117: Confusing autofill settings. Reported by Spencer Dailey on 2018-03-15
  • Low CVE-2018-6084: Incorrect use of Distributed Objects in Google Software Updater on MacOS. Reported by Ian Beer of Google Project Zero on 2018-03-15
Submit