If I allow public access to a remote control program (SSH, teamviewer, remote desktop connection, etc) is there any risk of damage that can't be fixed through reinstalling the operating system? Do any seriously destructive exploits exist for either Windows or Linux that someone could execute given remote access?
1
-
they could plant un-removable malware in any firmware on the computer– Neil McGuiganApr 23, 2016 at 22:41
Add a comment
|
2 Answers
There is no risk of physical hardware damage by allowing someone remote access to a computer. At most, someone could corrupt the OS so bad that you'd have to reload it. But it sounds like you're prepared for that.
The absolute worst that anybody could do is crap it up with some nasty viruses. If you're going to allow the public to use it, I would physically air-gap the computer from the rest of your network so there is no possible way for a virus to infect any other system you may have. This would involve a completely independent path to your ISP. If that's not possible, then a completely isolated DMZ would be the next best option. Do not share the network this computer will be on with any other computers you have.
Also, you should be aware that there are some particularly nasty boot sector viruses that can infect the slack space on a hard drive. Such viruses do not go away simply by reinstalling the OS. You have to boot to a Linux distro and wipe the drive to get rid of those.
Along the virus thread, there are some firmware viruses out there as well. You can block these by using the Secure Boot feature of your BIOS and booting Windows in EFI mode. You will need Windows 8/Server 2012 or greater for this though. Also, some business-class computers from Dell and HP have a setting in the BIOS to require signed firmware updates which predates Secure Boot. Those can block firmware viruses even on Win7/Server 2008 and lower which do not support Secure Boot.
Other than that, no, there are no exploits out there that could destroy the computer's hardware.
answered Apr 22, 2016 at 16:45
-
I'm not sure this is accurate. It's quite possible to run overclocking software with settings likely to damage physical hardware, for example. Apr 22, 2016 at 16:49
-
I'd say that risk is non-existent these days. I've only ever been able to physically roast a computer once in my life, and that was back in the AMD Athlon XP days when they did not throttle on overheat the way they do now. If someone knows a way to destroy modern hardware by pushing the clock too far I'd love to see it. Apr 22, 2016 at 17:30
-
This is all useful to know, but I'm not limiting this to hardware problems. I'm also concerned about network problems, which you've covered, but also firmware problems. In the 90s, there was a trojan called CIH which corrupted the BIOS on the motherboard. This required repairing from the manufacturer.– DaffyApr 22, 2016 at 17:40
-
-
1@Daffy - So do what the rest of the world does. Configure a VPN server, and only allow external access to your network, through the a VPN connection. Having a single account and service to secure it a great dealer easier then trying to do that half a dozen services.– RamhoundApr 22, 2016 at 20:38
Haswell and later CPUs can be damaged by Prime 95, if run for long periods of time.
Combine this with the maximum overclock that you can get, and hardware damage could occur.
From Raja@Asus link
Praz nailed it really. The newer versions of Prime load in a way that they are > only safe to run at near stock settings. The server processors actually downclock when AVX2 is detected to retain their TDP rating. On the desktop we're free to play and the thing most people don't know is how much current these routines can generate. It can be lethal for a CPU to see that level of > current for prolonged periods.
