The 5 Worst IoT Hacks and Vulnerabilities in Recorded History


April 27, 2017

IoT hacks are unbelievably effective. By leveraging thousands (if not millions) of insecure connected devices, hackers can produce DDoS attacks that can cripple our infrastructure, systems, and way of life. Or, attackers can go straight for the kill by directly exploiting a device and using it as a gateway to deeper levels on a network where they gather sensitive and valuable private data.

And things are about to get worse. Forbes predicts that by 2025, we’ll have over 80 billion smart devices on the internet. Much of the embedded firmware running on these devices is insecure and highly vulnerable, leaving an indeterminate number of critical systems and data around the world at risk.

If you’re in the IoT space, read on to understand these hacks and vulnerabilities. They’ll open your eyes to how the future could (and likely will) look and prompt consideration on why devices must be secured today.

Here are the 5 Worst IoT Hacks and Vulnerabilities in Recorded History:

  1. The Mirai Botnet (aka Dyn Attack) – According to PC Magazine, “Millions of insecure Internet of Things (IoT) devices were swept into the Mirai botnet and used to massively overload domain name system (DNS) provider Dyn with a DDoS attack. The attack knocked out Etsy, GitHub, Netflix, Shopify, SoundCloud, Spotify, Twitter, and a ton of other major websites. Here are four straightforward loT security lessons that businesses can take from the incident:
    • Devices that cannot have their software, passwords, or firmware updated should never be implemented.
    • Changing the default username and password should be mandatory for the installation of any device on the Internet.
    • Passwords for IoT devices should be unique per device, especially when they are connected to the Internet.
    • Always patch IoT devices with the latest software and firmware updates to mitigate vulnerabilities.”

  1. The Hackable Cardiac Devices from St. Jude – Early this year, CNN wrote, “The FDA confirmed that St. Jude Medical's implantable cardiac devices have vulnerabilities that could allow a hacker to access a device. Once in, they could deplete the battery or administer incorrect pacing or shocks, the FDA said.

    The devices, like pacemakers and defibrillators, are used to monitor and control patients' heart functions and prevent heart attacks.”

    The article continued to say, “The vulnerability occurred in the transmitter that reads the device's data and remotely shares it with physicians. The FDA said hackers could control a device by accessing its transmitter.”

  1. The Owlet WiFi Baby Heart Monitor Vulnerabilities – Right behind the St. Jude cardiac devices is Owlet WiFi baby heart monitor. According to Cesare Garlati, Chief Security Strategist at the prpl Foundation: “This latest case is another example of how devices with the best of intentions, such as alerting parents when their babies experience heart troubles, can turn dangerous if taken advantage of by a sinister party.  Sadly, this is more often than not in the case of embedded computing within so-called smart devices.  The connectivity element makes them exploitable and if manufacturers and developers don’t consider this and take extra steps to secure devices at the hardware layer, these are stories that we will, unfortunately, keep hearing.”

  1. The TRENDnet Webcam Hack – And, continuing with the baby theme, TechNewsWorld reports, “TRENDnet marketed its SecurView cameras for various uses ranging from home security to baby monitoring and claimed they were secure, the FTC said. However, they had faulty software that let anyone who obtained a camera's IP address look through it -- and sometimes listen as well.

    Further, from at least April 2010 [until about January 2012], TRENDnet transmitted user login credentials in clear, readable text over the Internet, and its mobile apps for the cameras stored consumers' login information in clear, readable text on their mobile devices, the FTC said.

    It is basic security practice to secure IP addresses against hacking and to encrypt login credentials or at least password-protect them, and TRENDnet's failure to do so was surprising.”

  1.  The Jeep Hack – The IBM SecurityIntelligence website reported the Jeep hack a few years ago, saying, “It was just one, but it was enough. In July [2015], a team of researchers was able to take total control of a Jeep SUV using the vehicle’s CAN bus. By exploiting a firmware update vulnerability, they hijacked the vehicle over the Sprint cellular network and discovered they could make it speed up, slow down and even veer off the road. It’s proof of concept for emerging Internet of Things (IoT) hacks: While companies often ignore the security of peripheral devices or networks, the consequences can be disastrous.”

 

Knowing is half the battle: find out how secure your firmware really is.