The Internet of Things has become more of a joke lately because of the never ending styles of exploitation that these poor devices are being subjected to by malicious cybercriminals and hackers.
It is now widely believed that the IoT devices are seriously prone to cyber attacks as their various inherent vulnerabilities make them easy targets for attackers.
The latest flaw in the severely hyped IoT devices was discovered by a tech industry veteran Robert Stephens, who identified that his security camera could be compromised within 98 seconds only as soon as it gets connected to Wi-Fi.
This was merely an experiment from Stephens but even then he was cautious enough to rate his network as limited and isolated the camera from the rest of the network-connected devices so as to ensure that a DDoS attack is prevented.
When he was able to compromise the camera he carefully kept observing the traffic in order to check attempts from third-parties to control the vulnerable device.
However, he didn’t expect it to occur in less than two minutes’ time.
To his surprise, after 98 seconds, the camera was plagued with a Mirai type worm and it became apparent to Stephens that the default login and password were exposed.
The worm started checking out the device it had newly captured and completely downloaded itself on the camera.
If Stephens wasn’t wise enough to lock the device beforehand, he would have been in great trouble as the device would have become an open platform for malicious attackers to play their games.
The camera used for this experiment was a cheap one created by a company that is known for selling smartwatches for 12USD.
So, it is obvious that the camera wasn’t a very reliable one and was not created by a top-class brand.
Stephens stated that although this vulnerability in security cameras can be fixed with simple password change or a firmware update but not all users are aware of it and this also cannot be done in two minutes.
Here is a series of tweets from Stephens explaining what happened and how:
View image on Twitter
Rob Graham @ErrataRob
1/x: So I bought a surveillance camera
3/x: Within 5 minutes, it was compromised by the Mirai botnet/worm:
4/x: then grabs the processor info directly
5/x: looks for ‘wget’ or ‘tftp’ in order to download binaries the easy way
6/x: that doesn’t work, so has to download the virus binary the hard way
7/x: And when it’s done, it runs the binary, and the box is now officially infected:
8/x: Actually, it took 98 seconds for first infection
9/x: but by something that isn’t Mirai, but something else similar to it
10/x: This camera I got off http://Amazon.com for $55:https://www.amazon.com/gp/product/B00OYBB08M/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 …
720P Wi-Fi Security Camera Onvif 2.4, Infrared 50ft Night Vision for Indoor/Outdoor Waterproof CCTV
Security Camera Wireless, JideTech 1080*720 1.0 MegaPixel Network Dome Camera Supports Wi-Fi, Onvif 2.4, Infrared 50ft in Night for Indoor & Outdoor, Mini Style Specification of Security Camera…
11/x: Bah, I’ve got my isolation rules setup wrong, blocking outbound TCP, so I’ve been inadvertently preventing further infection
12/x: Ignore that last tweet. It appears that connecting to those ports is difficult anyway, even from another machine.
13/x: So I’ve got what appears to be two active infections (the shells with PID greater than 2000).
14/x: so after it loads the first stage Mirai, it then connects out to download the full virus, like from here: http://220.127.116.11/arm
15/x: once it downloads that, it runs it and starts spewing out SYN packets at a high rate of speed, looking for new victims
17/x: I think I’ve got my firewall configured correctly, blocking outbound port 23, so these shouldn’t be hitting the Internet.
18/x: Oooo, noooes, one of the infections killed the Telnet daemon and kicked me off!!! Jerks.
19/19: Time for bed. Powering off to power back on and play some more tomorrow.