{"id":6967,"date":"2018-09-12T13:57:39","date_gmt":"2018-09-12T11:57:39","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=6967"},"modified":"2018-09-18T00:39:04","modified_gmt":"2018-09-17T22:39:04","slug":"ccleaner-forces-update-from-v5-38-to-v5-46","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2018\/09\/12\/ccleaner-forces-update-from-v5-38-to-v5-46\/","title":{"rendered":"CCleaner forces update from v5.38 to v5.46"},"content":{"rendered":"

[German<\/a>]It seems that Piriform's CCleaner will be forced to be updates from old version 5.38 to version 5.46 \u2013 and the telemetry settings are switches on by default.<\/p>\n

<\/p>\n

\"\"About the CCleaner and the trouble it caused, I've published a lot of articles here in the blog. Since security provider AVAST took over developer Piriform in 2017, the mishaps have been increasing.<\/p>\n

The Telemetry thing and version 5.46<\/h2>\n

With the CCleaner version 5.45, Piriform had upgraded its telemetry data collection (see AVAST CCleaner 5.45 and Telemetry). After a big outcry among the users, Piriform decided to completely withdraw version 5.45 of the CCleaner at the beginning of August 2018.<\/p>\n

\"CCleaner\"
\n(Source: Talos)<\/p>\n

After the complete revision the CCleaner version 5.46 was released at the end of August 2018. The users should be able to adjust if and what the CCleaner does. I had summarized my thoughts in the article CCleaner V 5.46 with improved data settings<\/a> and assumed that (according to my blog posts) nobody actually lets the software on his systems anymore.<\/p>\n

Automatic update to v5.46<\/h2>\n

This night, several e-mails arrived from German blog reader Georg S., who drew my attention to another ccleaner story. Georg S. wrote in his first mail:<\/p>\n

just now I had to find out on 3 computers with Windows 7 Ultimate 64 bit that CCleaner Slim version 5.38 has been updated yesterday (2018-09-10) automatically to v5.46.<\/p>\n

I had definitely deselected the option for automatic updates. If Avast did this systematically, then the data sniffing has reached a new peak.<\/p>\n

In version 5.46 Slim (Settings –> Privacy) the function \"Help improve CCleaner by sending anonymous usage\" was activated. In the Control Panel (Programs and Functions), I have sorted the installed software updates by date. I discovered that CCleaner 5.46 has been installed.<\/p><\/blockquote>\n

\"CCleaner<\/p>\n

Georg has send me the above screenshot from Control panel showing the installed update. In another mail the blog reader wrote:<\/p>\n

also my Win 10 home tablet is affected by the \"misery\". I installed CCleaner v5.38 over v5.46 (works fine), made the usual settings and didn't have to delete an ominous \"Avast-Pirifom\" cookie, but on all Win 7 PCs.<\/p>\n

I will now observe the behavior of CCleaner to possibly be able to reproduce the behavior.<\/p>\n

So all 4 computers were\/are affected!<\/p>\n

Today I will restore the Win 7 images from September 1st and install yesterday's Windows and missing software updates.<\/p><\/blockquote>\n

Of course it's a very unpleasant behavior – of course I don't notice it, because I don't let this software on my systems. Later Georg S. added the following:<\/p>\n

meanwhile I restored the image from 2018-09-01 on one of the affected Win 7-PCs and CCleaner was updated from 5.38 Slim to 5.46 again, although the option for automatic updates was deselected.<\/p>\n

Again at 5.46 the data transfer is activated without any query. Thus the \"silent\" update is automatically activated by Avast – an absolute No Go.<\/p>\n

I will reinstall the image and uninstall CCleaner 5.38 immediately!<\/p>\n

I have used CCleaner to comfortably \"clean up\" the registry under a user interface, which is sometimes difficult to find under Win 7 itself.<\/p><\/blockquote>\n

Shortly after publishing the German edition of this blog post, I got confirmation from another blog reader, that it wasn't a single incident. So I don't need to add further comments to my article \u2013 it's now up to you, to judge, whether you trust CCleaner anymore. It's the old thing: If you are using snake oil, your hands get dirthy with that.<\/p>\n

Addendum: CCleaner security issues<\/h2>\n

Due to the fact, that some CCleaner lovers are take my (German) blog post about that tool to personally, I let execute the portable version of CCleaner within my security test bed. This test bed shows, whether a program is vulnerable for DLL hijacking or other things. Here is a screenshot:<\/p>\n

\"CCleaner-Sicherheitswarnung\"<\/p>\n

One DLL hijacking mine after the other went up during executing CCleaner (portable edition, the installable version has even more issues).\u00a0The problem is that CCleaner can be hijacked by malware with very simple means.\u00a0In order to uninstall something in Windows (always used as an argument why some users need the tool), CCleaner needs administrator rights. But then malware can piggyback via DLL hijacking to gain administrator privileges.\u00a0Some background information about the security problems with DLL hijacking including information about the testbed can be found here<\/a>.<\/p>\n

Similar articles<\/strong>
\nCCleaner has been infected with malware<\/a>
\nCCleaner comes mit AVAST PUP<\/a>
\nAVAST CCleaner 5.45 and the telemetry thing<\/a>
\nCCleaner 5.45 pulled and other peculiarities<\/a>
\nCCleaner V 5.46 with improved data settings<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]It seems that Piriform's CCleaner will be forced to be updates from old version 5.38 to version 5.46 \u2013 and the telemetry settings are switches on by default.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1547,22],"tags":[1041,47,195],"class_list":["post-6967","post","type-post","status-publish","format-standard","hentry","category-software","category-update","tag-ccleaner","tag-issue","tag-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/6967","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=6967"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/6967\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=6967"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=6967"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=6967"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}