Skip to main content

Chrome Releases Stable Channel Update for Desktop Tuesday, March 6, 2018


Jasper_The_Rasper
Moderator
Forum|alt.badge.img+54

Stable Channel Update for Desktop

Tuesday, March 6, 2018  
The Chrome team is delighted to announce the promotion of Chrome 65 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks. Chrome 65.0.3325.146 contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 65. Security Fixes and Rewards
 
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 45 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
 
[$5000][758848] High CVE-2017-11215: Use after free in Flash. Reported by JieZeng of Tencent Zhanlu Lab on 2017-08-25
[$5000][758863] High CVE-2017-11225: Use after free in Flash. Reported by JieZeng of Tencent Zhanlu Lab on 2017-08-25
[$3000][780919] High CVE-2018-6060: Use after free in Blink. Reported by Omair on 2017-11-02
[$3000][794091] High CVE-2018-6061: Race condition in V8. Reported by Guang Gong of Alpha Team, Qihoo 360 on 2017-12-12
[$1000][780104] High CVE-2018-6062: Heap buffer overflow in Skia. Reported by Anonymous on 2017-10-31
[$N/A][789959] High CVE-2018-6057: Incorrect permissions on shared memory. Reported by Gal Beniamini of Google Project Zero on 2017-11-30
[$N/A][792900] High CVE-2018-6063: Incorrect permissions on shared memory. Reported by Gal Beniamini of Google Project Zero on 2017-12-07
[$N/A][798644] High CVE-2018-6064: Type confusion in V8. Reported by lokihardt of Google Project Zero on 2018-01-03
[$N/A][808192] High CVE-2018-6065: Integer overflow in V8. Reported by Mark Brand of Google Project Zero on 2018-02-01
 
Full Article.

6 replies

TripleHelix
Moderator
Forum|alt.badge.img+63
  • Moderator
  • 9178 replies
  • March 7, 2018
Got the latest version via Internal Update!
 


 
Thanks,
 
Daniel
 

Ssherjj
Moderator
Forum|alt.badge.img+62
  • Moderator
  • 21950 replies
  • March 7, 2018
Super I am all updated now too. Thanks Jasper!

DTMT
Popular Voice
Forum|alt.badge.img+24
  • Popular Voice
  • 104 replies
  • March 9, 2018
Received a report from one of our HTG partners that with the latest release of Chrome, when Webroot is enabled, CPU spikes and systems become extremely unresponsive. The partner mentioned they were receiving little to no response from Webroot support and were looking at dropping Webroot.
 
I had not experienced the issue, but then upgraded from v64.xx to v65.xx and was able to replicate the issue.  It actually isn't Webroot itself that is the issue: It's the Webroot Chrome Extension.  I downloaded it from the Chrome store to make sure I was running this in addition to antivirus, and when I enabled it, my system bogged down so hard I had to use a command window to taskkill Chrome (Task Manager wasn't responsive enough).  Disabling the Webroot plugin fixed the issue, so I turned it back on, just to confirm.  Immediately, my system spiked again, going from single-digit CPU usage to betwen 40-80% and the system again bogged down.  Exiting Webroot but leaving the Chrome extension on did not resolve the issue, leaving the system just as sluggish, so I am concluding it is the extension, not the endpoint agent.
 
Whatever is going on, the Webroot Chrome extension is not playing nice with v65 of Chrome, or the other way around.
 
EDIT: Opened Ticket 150948

Ssherjj
Moderator
Forum|alt.badge.img+62
  • Moderator
  • 21950 replies
  • March 9, 2018
Hello DTMT,
 
Some Webroot Consumers have been reporting this issue as well. I thought the updated Webroot v9.0.19.43 had a fix for the issue that you are discribing. Personally I am not having any trouble opening the Task Manager with Chrome. But like I said some still are.
 
Sorry for all the inconciences. Maybe it would be quicker to call the Business Support Team?
Tel: https://tel:+18662548400
 
Hope this helps somewhat?
Version 9.0.19.43 (Released January 24th, 2018)
Version 9.0.19.43 (Released January 24th, 2018)

DTMT
Popular Voice
Forum|alt.badge.img+24
  • Popular Voice
  • 104 replies
  • March 9, 2018
@wrote:
Hello DTMT,
 
Some Webroot Consumers have been reporting this issue as well. I thought the updated Webroot v9.0.19.43 had a fix for the issue that you are discribing. Personally I am not having any trouble opening the Task Manager with Chrome. But like I said some still are.
 
Sorry for all the inconciences. Maybe it would be quicker to call the Business Support Team?
Tel: https://tel:+18662548400
 
Hope this helps somewhat?
Version 9.0.19.43 (Released January 24th, 2018)
Version 9.0.19.43 (Released January 24th, 2018)
At this point, I am not having an issue with my clients, though we are running 9.0.19.43.  I believe we are not because with the changes Google made to Chrome extension requirements (it must be downloaded from the Chrome Web Store now), it is my belief that at some point in the recent past, new Webroot agent installers are not only no longer bundled with the Webroot extension, but likely even uninstall versions of the Chrome extension prior to the one available from the Web Store (thus we have not had any client complaints -I can only think the other partner has some way of distributing the extension).
 
I only downloaded the extension for testing purposes, and wished to make the issue known to IT people, and open a ticket to give the issue availability; fortunately, it isn't affecting any of my clients at the moment, or at least, we have had no reports (which would be very likely if the problem is present, Chrome is generally a required install on our new Windows 10 workstations to give clients an alternative to Edge).

Ssherjj
Moderator
Forum|alt.badge.img+62
  • Moderator
  • 21950 replies
  • March 9, 2018
@ wrote:
@wrote:
Hello DTMT,
 
Some Webroot Consumers have been reporting this issue as well. I thought the updated Webroot v9.0.19.43 had a fix for the issue that you are discribing. Personally I am not having any trouble opening the Task Manager with Chrome. But like I said some still are.
 
Sorry for all the inconciences. Maybe it would be quicker to call the Business Support Team?
Tel: https://tel:+18662548400
 
Hope this helps somewhat?
Version 9.0.19.43 (Released January 24th, 2018)
Version 9.0.19.43 (Released January 24th, 2018)
At this point, I am not having an issue with my clients, though we are running 9.0.19.43.  I believe we are not because with the changes Google made to Chrome extension requirements (it must be downloaded from the Chrome Web Store now), it is my belief that at some point in the recent past, new Webroot agent installers are not only no longer bundled with the Webroot extension, but likely even uninstall versions of the Chrome extension prior to the one available from the Web Store (thus we have not had any client complaints -I can only think the other partner has some way of distributing the extension).
 
I only downloaded the extension for testing purposes, and wished to make the issue known to IT people, and open a ticket to give the issue availability; fortunately, it isn't affecting any of my clients at the moment, or at least, we have had no reports (which would be very likely if the problem is present, Chrome is generally a required install on our new Windows 10 workstations to give clients an alternative to Edge).
Thank you DTMT, for the clarifications!

Reply