Backdoor In RuggedOS Systems: Infrastructure, Military Systems Vulnerable 154
Posted
by
Unknown Lamer
from the steal-me-up-some-electricity dept.
from the steal-me-up-some-electricity dept.
FhnuZoag writes "A backdoor has been found in Canadian based RuggedCom's 'Rugged Operating System', providing easy access to anyone with the devices's MAC address — something often publically displayed. Rugged OS is being used in a wide range of applications, including traffic control, power generation, and even U.S. Navy bases. The backdoor was first found over a year ago, and RuggedCom have so far refused to patch out the exploit."
The exploit is trivial: each device has a permanent "factory" user, and an automatically generated password derived from the MAC.
exploit (Score:5, Insightful)
Looks like to exploit this, you need the MAC addrs.
1) One way is to be on the same LAN segment and watch a sniffer. This means you're already dead because you've lost physical security.
2) Another way is to telnet (FREAKING telnet in 2012?) into the device and the MAC is in the MOTD. This means you're already dead because you've lost all network security. What kind of madman allows telnet traffic thru a firewall in 2012? What kind of a madman allows unrestricted internet access to an embedded control device?
3) If you manage to somehow own a plain ole PC on a scada network, now you can own embedded control devices. But having an owned PC on your network means you're dead anyway.
I'm still struggling to figure out how a live, well run network could be in danger. What I mean is to implement this exploit takes a system that is already more screwed up than anything you could do with the exploit.
Especially things with factory supplied backdoor (Score:5, Insightful)
Nothing is 100% secure. Nothing. At. All.
Especially those things with a factory supplied backdoor. Regardless of the complexity of the password, regardless of how the marketing guys try to spin it as a "maintenance portal" or whatever they are calling it (assuming of course customers knew it was there), such a thing is essentially a backdoor.
Hopefully this was something that customers were aware of and something that customers could disable. Or more optimistically a debugging feature customers would have to enable for a session while in direct communication with the factory. Even so a hypothetically generate-able password is troubling.
Re:exploit (Score:5, Insightful)
4) brute force the password, knowing that only 3 bytes are unique to the device.
Engineers overlooking the obvious design (Score:4, Insightful)
The obvious correct hardware design was a simple switch (on the device) that allows usage of a default password. That way, you ensure both that you can put maintenance to the device in the future, whilst maintaining daily security.
Re:Nothing is 100% secure. (Score:5, Insightful)
>>>the failure to address it.
I suppose this is why OSS advocates claim closed-source is bad? You can't fix the problem yourself, and if the company refuses to do it, then you're stuck.
Re:Engineers overlooking the obvious design (Score:5, Insightful)
Also when the switch is flipped it should not perform its normal work.
That way it cannot be left in that mode.
Re:exploit (Score:5, Insightful)
Barring rate limiting, or other protection mechanisms (unlikely on a SCADA device) I'd estimate that a brute force attack on a 100mb/s link is going to be done and dusted in a matter of minutes rather than hours or days.
Re:Nothing is 100% secure. (Score:5, Insightful)
I think you're giving them far too much credit.
A password generated using an externally visible attribute of the device is pure incompetence and making stupid decisions.
This isn't about Beardo going away and losing the password, it's about someone making one of those shockingly stupid decisions about convenience over security which leads to security through obscurity.
As TFS says, this is bordering on a trivial exploit since you can likely hack any and all devices running this OS merely by figuring out its MAC address.
This is just blatantly moronic. If you're marketing yourself for "mission critical", don't do something this stupid.
Re:Nothing is 100% secure. (Score:4, Insightful)
Never bet on a pool game against anyone named after a state.
Re:Nothing is 100% secure. (Score:5, Insightful)
Never get involved in a software project where the team leader says either "agile" or "scrum" in every second sentence.
Re:Nothing is 100% secure. (Score:4, Insightful)
Right, which means anyone with a pair of overalls can change the light controller.
Re:Nothing is 100% secure. (Score:4, Insightful)