Re:CCleaner Command and Control Causes Concern
by 0x0 on Wednesday September 20, 2017 @07:53PM
(#15299428)
Can you imagine the havoc you could create if you compromise microsoft+samsung+vmware+intel and push malware embedded in software+firmware updates that combine the (also a HN top post right now) Intel ME hack and perhaps a couple of the (also HN top post right now) broadcom wifi chip exploits?
Will we end up with a setup where every system within range of a wifi chip is instantly and persistently compromised? Could we even recover from that?
Re:CCleaner Command and Control Causes Concern
by milesokeefe on Wednesday September 20, 2017 @08:22PM
(#15299579)
Yes, so many/most phones and laptops would be compromised. But there are also plenty of computers in every form that aren't plugged into anything at all and completely invulnerable.
It would be devastating but nothing we couldn't rebuild from.
Re:CCleaner Command and Control Causes Concern
by outoftacos on Wednesday September 20, 2017 @08:39PM
(#15299648)
You mean like desktops? That are unplugged? How many of those do you think are sitting around? How old is the version of Windows on them do you think?
If your recovery strategy is "drive as fast as you can to the thrift shop" then I don't know how effective "rebuilding" would be. This is fucking terrifying.
Re:CCleaner Command and Control Causes Concern
by milesokeefe on Wednesday September 20, 2017 @08:25PM
(#15299590)
If by "isn't on" you mean "turned off by the OS", that wouldn't do anything. Intel ME operates despite whatever the OS is doing. You'd have to physically disconnect the modem, put the device in a faraday cage, completely remove power source, etc.
Re:CCleaner Command and Control Causes Concern
by raesene6 on Thursday September 21, 2017 @05:55AM
(#15301914)
Supply chain attacks are an obvious avenue for high-end attackers, where their direct targets are hardened, so I guess we'll see more of these going forward.
Whilst companies like Microsoft can likely afford to harden their software update systems well enough to deter this, I do wonder what impact it'll have if smaller software providers/open source software providers who can't afford high-end OpSec teams start getting targeted.
Realistically a lot of software auto-updates these days so it's a nice avenue for attackers to exploit...
Re:CCleaner Command and Control Causes Concern
by sengork on Wednesday September 20, 2017 @08:54PM
(#15299721)
Yes, tools like Comodo firewall by default are set to be quiet and prevent end user prompts as much as possible.
Regardless the amount of components (whether it be OS, software or website elements) which attempt connecting is overwhelming for even a non-average tech savvy user.
For example install https://pi-hole.net/ and you'll no doubt realise that most of the DNS queries traversing your home network are not directly made by the end-user.
Re:CCleaner Command and Control Causes Concern
by raesene6 on Thursday September 21, 2017 @05:52AM
(#15301899)
You can do it in Windows with something like glasswire, or on OSX with Little snitch or equivalent.
I run glasswire, and regularly see legitimate traffic from odd sounding processes. A non-technical user would have zero chance of determining what was legitimate and what wasn't.
So whilst it is handy for technical users (who are willing to put in the effort to check all the various processes that make network access) it's not likely to work well for the wider user population
Re:CCleaner Command and Control Causes Concern
by lathiat on Wednesday September 20, 2017 @09:50PM
(#15299975)
The reality is that the average majority consumer would be so annoyed by such things that they would be ineffective. And at best most likely become trained just to hit YES.
Even as a technical user, my reaction to windows privilege escalation is pretty much just to smash yes.
Like all good things, there is a balance... and there will always be people keen to be more attuned to whats happening.
Re:CCleaner Command and Control Causes Concern
by bob33212 on Wednesday September 20, 2017 @08:51PM
(#15299708)
These attackers are after the IT blueprints of other organizations. So that they can build a hibernating bot inventory. They can then sell pwned corporate computers to 3rd parties for BTC. Phishing and Spear Phishing doesn't work well on pro users. But this does.
Will we end up with a setup where every system within range of a wifi chip is instantly and persistently compromised? Could we even recover from that?
*every system within range of a wifi chip and connected to a power source
It would be devastating but nothing we couldn't rebuild from.
If your recovery strategy is "drive as fast as you can to the thrift shop" then I don't know how effective "rebuilding" would be. This is fucking terrifying.
I find that more interesting than the article itself. Some unknown entity just happened to hack the command server and drop a dump of it in their lap?
Whilst companies like Microsoft can likely afford to harden their software update systems well enough to deter this, I do wonder what impact it'll have if smaller software providers/open source software providers who can't afford high-end OpSec teams start getting targeted.
Realistically a lot of software auto-updates these days so it's a nice avenue for attackers to exploit...
operating systems like windows give no indication to the ordinary user what internet connections they are making either legitimately themselves or
from software installed separately and giving users the opportunity to review and grant or deny access.
If ALL connections were transparent it would be much easier to see what was not appropriate.
Operating systems should say that a connection is being made and for what purpose and the user given the opportunity to grant or deny.
This is what i liked about Sophos' original interface sadly gone by the wayside.
Regardless the amount of components (whether it be OS, software or website elements) which attempt connecting is overwhelming for even a non-average tech savvy user.
For example install https://pi-hole.net/ and you'll no doubt realise that most of the DNS queries traversing your home network are not directly made by the end-user.
I run glasswire, and regularly see legitimate traffic from odd sounding processes. A non-technical user would have zero chance of determining what was legitimate and what wasn't.
So whilst it is handy for technical users (who are willing to put in the effort to check all the various processes that make network access) it's not likely to work well for the wider user population
Even as a technical user, my reaction to windows privilege escalation is pretty much just to smash yes.
Like all good things, there is a balance... and there will always be people keen to be more attuned to whats happening.