21
Oct 16

Hacked Cameras, DVRs Powered Today’s Massive Internet Outage

A massive and sustained Internet attack that has caused outages and network congestion today for a large number of Web sites was launched with the help of hacked “Internet of Things” (IoT) devices, such as CCTV video cameras and digital video recorders, new data suggests.

Earlier today cyber criminals began training their attack cannons on Dyn, an Internet infrastructure company that provides critical technology services to some of the Internet’s top destinations. The attack began creating problems for Internet users reaching an array of sites, including Twitter, Amazon, Tumblr, Reddit, Spotify and Netflix.

l3outage

A depiction of the outages caused by today’s attacks on Dyn, an Internet infrastructure company. Source: Level3 Communications.

At first, it was unclear who or what was behind the attack on Dyn. But over the past few hours, at least one computer security firm has come out saying the attack involved Mirai, the same malware strain that was used in the record 620 Gpbs attack on my site last month. At the end September 2016, the hacker responsible for creating the Mirai malware released the source code for it, effectively letting anyone build their own attack army using Mirai.

Mirai scours the Web for IoT devices protected by little more than factory-default usernames and passwords, and then enlists the devices in attacks that hurl junk traffic at an online target until it can no longer accommodate legitimate visitors or users.

According to researchers at security firm Flashpoint, today’s attack was launched at least in part by a Mirai-based botnet. Allison Nixon, director of research at Flashpoint, said the botnet used in today’s ongoing attack is built on the backs of hacked IoT devices — mainly compromised digital video recorders (DVRs) and IP cameras made by a Chinese hi-tech company called XiongMai Technologies. The components that XiongMai makes are sold downstream to vendors who then use it in their own products.

“It’s remarkable that virtually an entire company’s product line has just been turned into a botnet that is now attacking the United States,” Nixon said, noting that Flashpoint hasn’t ruled out the possibility of multiple botnets being involved in the attack on Dyn.

“At least one Mirai [control server] issued an attack command to hit Dyn,” Nixon said. “Some people are theorizing that there were multiple botnets involved here. What we can say is that we’ve seen a Mirai botnet participating in the attack.”

As I noted earlier this month in Europe to Push New Security Rules Amid IoT Mess, many of these products from XiongMai and other makers of inexpensive, mass-produced IoT devices are essentially unfixable, and will remain a danger to others unless and until they are completely unplugged from the Internet.

That’s because while many of these devices allow users to change the default usernames and passwords on a Web-based administration panel that ships with the products, those machines can still be reached via more obscure, less user-friendly communications services called “Telnet” and “SSH.”

Telnet and SSH are command-line, text-based interfaces that are typically accessed via a command prompt (e.g., in Microsoft Windows, a user could click Start, and in the search box type “cmd.exe” to launch a command prompt, and then type “telnet” to reach a username and password prompt at the target host).

“The issue with these particular devices is that a user cannot feasibly change this password,” Flashpoint’s Zach Wikholm told KrebsOnSecurity. “The password is hardcoded into the firmware, and the tools necessary to disable it are not present. Even worse, the web interface is not aware that these credentials even exist.”

Flashpoint’s researchers said they scanned the Internet on Oct. 6 for systems that showed signs of running the vulnerable hardware, and found more than 515,000 of them were vulnerable to the flaws they discovered.

“I truly think this IoT infrastructure is very dangerous on the whole and does deserve attention from anyone who can take action,” Flashpoint’s Nixon said.

It’s unclear what it will take to get a handle on the security problems introduced by millions of insecure IoT devices that are ripe for being abused in these sorts of assaults.

As I noted in The Democratization of Censorship, to address the threat from the mass-proliferation of hardware devices such as Internet routers, DVRs and IP cameras that ship with default-insecure settings, we probably need an industry security association, with published standards that all members adhere to and are audited against periodically.

The wholesalers and retailers of these devices might then be encouraged to shift their focus toward buying and promoting connected devices which have this industry security association seal of approval. Consumers also would need to be educated to look for that seal of approval. Something like Underwriters Laboratories (UL), but for the Internet, perhaps.

Until then, these insecure IoT devices are going to stick around like a bad rash — unless and until there is a major, global effort to recall and remove vulnerable systems from the Internet. In my humble opinion, this global cleanup effort should be funded mainly by the companies that are dumping these cheap, poorly-secured hardware devices onto the market in an apparent bid to own the market. Well, they should be made to own the cleanup efforts as well.

Devices infected with Mirai are instructed to scour the Internet for IoT devices protected by more than 60 default usernames and passwords. The entire list of those passwords — and my best approximation of which firms are responsible for producing those hardware devices — can be found at my story, Who Makes the IoT Things Under Attack.

Tags: , , , , , , ,

63 comments

  1. I don’t believe Telnet or SSH qualify as obscure, millions of people use them every day.

    It’s pretty dumb to not randomize the password before shipping, but this problem seems relatively trivial to fix.

    • They’re relatively obscure for most people buying and using these shoddily-secured IOT devices. Alas, the people who DO know what telnet and SSH are probably are not part of the problem.

  2. Can’t residential ISPs block telnet and ssh by default?

    • You would think that residential ISPs would block commonly used “inbound” ports, or at least the range formerly called “well known services” (0 through 1024).

      Sadly, most residential ISPs do not make this effort. I know that my ISP does not make this effort. I have been seeing port 22 and 23 probes increase since the Mirai exploit was released. I am now seeing those probes “on average” about 2 every minute of the day. Fortunately I do not have “exposed” IoT devices. I have a firewall that I fully control.

      • The question is why are these ports open on IoT devices? Clearly if ISPs block the 0-1024 range manufacturers will just move to a higher range. This will only solve the problem temporarily.

      • I’m thinking something the other way around. If an ISP sees that one of their subscribers are participating in such an attack, can’t they take some action at that time, like block the traffic and contact the subscriber.

        Going even further, if the victims of these attacks know all the IPs where the traffic is coming from (which I know is not always the case), then couldn’t some big-name website obtain that list and when someone known to be participating in the attack visits that popular website they see a banner that politely asks them to be a good internet citizen?

  3. Does anyone know what an end user might experience if they were browsing the web at the same time their IoT device was commanded to participate in a Mirai attack?

    I’m assuming they wouldn’t notice it except for some sluggishness, unless they had some network traffic program that alerted them to an outbound stream above a certain level, etc.

    Also, if the Krebs hit was 620 gbps and there were approx 515,000 infected devices, that’s 1.2 mbps on average. Does that sound right? I apologize if Brian already covered this previously.

    Finally, does anyone know of a good traffic analyzer program? I use NetWorx but I’m guessing Mirai traffic wouldn’t have been picked up by this program had I been infected. Windows Resource Monitor seems pretty thorough but lacks notification features.

    • You’ll need something at the edge of your network to analyze traffic from other devices; your windows machine isn’t capable of seeing traffic between other devices on your network and the internet (with one unlikely exception)

      You basically need a router that can tell you how much traffic is going in and out of your network. Ideally something that tells you how much internet traffic is coming from each device. dd-wrt and pfSense are both router OSs and have some capability of monitoring traffic.

      Also, unless I’m mistaken (like if UPnP is at play), you would have to have your IP camera or DVR publicly exposed on the internet for your device to be hacked; you would have to either have your camera plugged straight into your modem, or have explicitly made an exception in your router to allow traffic to the camera.

  4. Is there any sound detail on motive or what industry will be targeted?

  5. As far as I understand, each hardware vendor gets allotted a certain range of MAC addresses for their hardware. Can we just blacklist the offending vendor’s MAC mask in gateways and neuter their devices across the internet? Obviously they would no longer work but it seems like a small price to pay…

    • MAC addresses aren’t used in routing between networks. Routers use IP addresses when making routing decisions and the source MAC address will change from hop to hop as the packet traverses networks. Unfortunately, this won’t work

  6. @Pleamonn Take a look at Schneier on Security for some ideas on the intent behind this attack: http://www.schneier.com/blog/archives/2016/09/someone_is_lear.html

  7. Telnet is not installed by default in Windows. It has to be installed separately from //add/remove windows components// from control panel

  8. I’d like to see evidence of who these “state actors” are, before crying about the sky falling.

    HEY! Where’s John Mcafee? he’s likely somewhere in Belize, running a warehouse of hackers.

    Probably out of anger for losing the nomination for US President.

    But, he’s far too smart to pull the #BlamePutin, BS.

Leave a comment