Slashdot Mirror


Ask Slashdot: Is My IoT Device Part of a Botnet?

As our DVRs, cameras, and routers join the Internet of Things, long-time Slashdot reader galgon wonders if he's already been compromised: There has been a number of stories of IoT devices becoming part of botnets and being used in distributed denial of service attacks. If these devices are seemingly working correctly to the user, how would they ever know the device was compromised? Is there anything the average user can do to detect when they have a misbehaving device on their network?
I'm curious how many Slashdot readers are even using IoT devices -- so leave your best answers in the comments. How would you know if your IoT device is part of a botnet?

20 of 279 comments (clear)

  1. How do you know? by Pikoro · · Score: 4, Insightful

    If it's connected to the internet directly, and it has no built in security apart from "admin" "password", it's part of a botnet or soon will be.

    --
    "Freedom in the USA is not the ability to do what you want. It is the ability to stop others from doing what THEY want"
    1. Re:How do you know? by JaredOfEuropa · · Score: 5, Insightful

      Especially if that password
      - Is a default password that is the same for every device sold (these days a lot of equipment ships with unique random passwords)
      - Isn't changed by the user during setup
      - Can't be changed by the user. (What the hell, OpenElec?)

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    2. Re:How do you know? by hcs_$reboot · · Score: 4, Funny

      Just install Norton AV on it, and add McAfee to be sure. Then, even a botnet wouldn't want to anymore run on that device

      --
      Slashdot, fix the reply notifications... You won't get away with it...
    3. Re:How do you know? by Z00L00K · · Score: 5, Insightful

      If it needs to connect to a subscription service outside your home it has the potential to become part of a bot net.

      Can you trust your thermostat to not browse your files?

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    4. Re:How do you know? by Applehu+Akbar · · Score: 5, Funny

      Just install Norton AV on it, and add McAfee to be sure. Then, even a botnet wouldn't want to anymore run on that device

      Yeah, that's it! "Should I have run MacAfee on my FirstAlert online smoke detectors?" you say to yourself as you gaze at the remains of your house.

    5. Re:How do you know? by geekmux · · Score: 4, Interesting

      Just install Norton AV on it, and add McAfee to be sure. Then, even a botnet wouldn't want to anymore run on that device

      Yeah, that's it! "Should I have run MacAfee on my FirstAlert online smoke detectors?" you say to yourself as you gaze at the remains of your house.

      IoT or not, odd how you made me wonder if the smoke alarm itself has ever been the source of a fire...

      I need coffee. It's too early for this.

    6. Re:How do you know? by Shoten · · Score: 5, Insightful

      Openelec's entire file system is read only. Given the difficulty of installing something to the image when you want to, the potential for it to be easily and automatically owned by is very low.

      This is not a real thing...a device whose total storage capacity is read-only. Let's look at why.

      One: if it's all read-only, it can't have a variable password...accounts and passwords need to be hardcoded, because there's no way to store new or changed account information.

      Two: if it's at all configurable, you have the same problem: where do you store the configs?

      Three: guess what else you can't have if your file system is read-only? Software updates.

      Four: let's call a spade a spade here. A more accurate way to make the claim...regardless of how infeasible it would be for any device of significant functionality...is to say this: "Openelec's entire file system is meant to be read only." An innate characteristic of most security flaws is that they permit something that is not intended. It's important to not assume that intended functionality is inevitable and invulnerable. And in this case, that "read only" capability is nothing more than Linux permissions...it's not that the OS invariably is incapable of granting write permissions. In fact, all kinds of things are writing to the file system, I would bet...information about drive mounting, accounts, etc. The file system is not inherently read only.

      Assuming that system behavior when used in its intended fashion is also what happens when someone breaks the rules is the root of most security failures.

      And now, a citation, called "squashfs howto - make changes the read-only filesystem in OpenELEC"

      https://sites.google.com/site/...

      --

      For your security, this post has been encrypted with ROT-13, twice.
    7. Re: How do you know? by jcdr · · Score: 4, Informative

      OpenELEC FAQ disagree:
      http://wiki.openelec.tv/index....

      What is the SSH login?
      Shortcut: #SSH Login
      Currently the login into OpenELEC has fixed settings.
        Login: root
        Password: openelec

      How do I change the SSH password?
      Shortcut: #SSH Password change
      At the moment it's not possible to change the root password as it's held in a read-only filesystem. However, for the really security conscious advanced user, you can change the password if you build OpenELEC from source. Also you can consider logging in with ssh keys and disabling password logins.

    8. Re:How do you know? by Solandri · · Score: 4, Interesting

      I've been saying for over a decade now that at least one storage device on the computer should have a physical read-only switch. Some kind of jumper which needs to be moved, or a switch on the motherboard which needs to be physically flipped, before you can write to the device. The main OS could be stored there, while logs, configs, temp files, etc. stored on a different storage device. Security flaws like a buffer overflow would still allow access to some memory, but it'd be impossible to exploit it to modify the system to give you full root access upon reboot.

      That's the way things were in the 1970s and early 1980s, when RAM was incredibly expensive so the programming for most embedded systems was stored in ROM, using RAM only for operational data. I've only seen one modern embedded system function this way - you stored the OS on a SD card with the write-protect switch flipped, and used a second SD card for data storage.

  2. The "average" consumer? Of course not. by Anonymous Coward · · Score: 4, Insightful

    The "average" user has no idea and that's why they put IOT shit on their unsecured network in the first place, duh.

  3. Re:Am A Noob Too by Bert64 · · Score: 4, Interesting

    Keep routers and access points separate, there's no need for them to be the same device...
    Get a low power atom device to run something like pfsense, a cheap managed switch (the hp 1800 series are good and quiet), use any wireless ap as a dumb bridge so it doesnt need any routing capabilities.
    Create separate VLANs for guests and other untrusted devices, you can connect to devices here via the firewall but don't allow any outbound connections from the network containing these devices.
    Buy new wifi as/when (eg 802.11ac), add multiple access points to cover different areas if necessary (even in a small house, wifi doesn't travel well through floors) and link them together via ethernet. Use ethernet whenever possible, wifi is only for portable devices.
    You can also setup a VPN so you can connect to your stuff from outside, having authenticated using both a certificate and a user/pass. Far less chance of compromise than some unknown black box device from china.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  4. Finally a counter example by Enter+the+Shoggoth · · Score: 5, Insightful

    Is this the long sought after counter-example to Betteridge's Law where the response to a question mark is always "yes" ?

    --
    Andy Warhol got it right / Everybody gets the limelight
    Andy Warhol got it wrong / Fifteen minutes is too long.
  5. Re:Control and management by Zocalo · · Score: 4, Informative

    Pretty much this, and given how bad many IoT devices are, even if you do change the passwords, etc., it's safer to just assume that they already have been compromised, or that they will be. Since we're talking retrospectively here, set up some connection logging on your outbound router. See if there's anything in the logs that's not what you were expecting, bearing in mind that they'll almost certainly be phoning home to "check for updates" and "backup your data to the cloud" (AKA "monetize your data"). Done. A better approach would have been to be more proactive (because the typical SoHo router vendor sure as hell won't be); as a minimum lock down anything you don't need, put all the IoT type devices on a dedicated network away from the stuff that matters, and configure the router to send an alert when anything anomalous happens. Bonus points for things like implementing BCP38 locally so even when you are compromised at least tried to minimise the damage, enabling syslog and actually monitoring the output, and other basic security principles.

    --
    UNIX? They're not even circumcised! Savages!
  6. Re:Am A Noob Too by clickety6 · · Score: 5, Funny

    Thanks for the info. I've printed it out for my grandmother...

    --
    ----------------------------------- My Other Sig Is Hilarious -----------------------------------
  7. Re:Am A Noob Too by cfalcon · · Score: 5, Insightful

    > Keep routers and access points separate...
    > low power atom device to run something like pfsense
    > cheap managed switch
    > wireless ap as a dumb bridge
    > Create separate VLANs

    Once you're done making this server room you describe, you'll be in the .0000001% of people qualified to run an IoT device, many of which are BORN malicious and sending pictures of your bedroom/front lawn/children to a central server in China, a decent number of which are fundamentally insecure with no possible way to change passwords or a default password they forgot (or "forgot") to strip out that you can't fix, and at least some of which will fail to work on a VLAN that can only see the outside internet (for some goddamned reason, they want to ping a router or something).

    The short version is this: If you want your IoT devices to not be part of a botnet, DO NOT BUY ANY. Once you buy those components, you have to set them up. Then configure them. Then maintain them. And almost no one will jump through any of those hoops.

  8. Re:The "average" consumer? Of course not. by jandersen · · Score: 5, Insightful

    The "average" user has no idea and that's why they put IOT shit on their unsecured network in the first place, duh.

    The average user has no idea that there is something like "IoT" and that it is in any way different from the rest of "the internet". All they know is that it is "smart" to have an app on your phone that can turn on the heating and tell you the fridge is empty, and a TV that seems to understand what you want to watch, or a smart meter that tells you (and the utility company) how much gas and electricity you use up to the last minute. They won't know or care about the security implications until it goes badly wrong.

  9. Re:log files by nukenerd · · Score: 4, Insightful

    If a person is intelligent enough to perceive the need for a device, obtain the device and install the device

    They will perceive the "need" when a salesman or ad persuades them that they need it. They do not even need to be aware that the device will be part of the IoT, only that they "need" a toaster or whatever.

    They will obtain the device by pulling out their wallet. (Soon it will become impossible to obtain anything else.)

    They will install it by plugging it in (have you never installed a toaster before?).

    I don't know where you think intelligence comes into it.

  10. Re:Am A Noob Too by MMC+Monster · · Score: 5, Insightful

    Dude, I'm not a network technician but I've been putting computers together since the late 80s and have been running Linux OSs as my desktop OS for over a decade now...

    And I couldn't set up the network you described without some serious googling.

    How are we supposed to expect normal people to do it? Do routers come with VLAN set up out of the box, jailed so that it doesn't send data out of your network? Somehow I doubt it.

    Normal people are screwed, until routers are set up to manage IoT networks by default.

    And let's be real: Normal people aren't going to buy a separate access point if their router has Wifi built in.

    --
    Help! I'm a slashdot refugee.
  11. Find the device's online trail by beda · · Score: 4, Informative

    Infected devices usually try to spread the infection further and their scanning attempts on the Internet are often observed. There is for instance a dedicated website for IoT devices attacking Telnet ports or some more generic ones, such as the Internet Storm Center. If the IP address of your device is on the list, it is very likely that you have a problem.

  12. Excellent question with no answer! by Kludge · · Score: 4, Informative

    I have often wondered the answer to this question myself: how can I tell if a machine on my network is compromised?
    So I set up a Linux box as my primary router, and monitored all the traffic going through the box, and holy crap, there is a lot of stuff.
    Every time you hit a facebook web page, the javascript in there directs your browser to hit literally dozens of other web sites, and this is true of EVERY device in your house: your wife's laptop, your son's smartphone, your dog's water bowl. When you watch a video on Netflix video, the video player hits a dozen different servers at once, and those connections come and go constantly, old ones are closed, new ones opened to different servers throughout the world with all kinds of different names. And, of course a modern computer or smartphone uses all kinds of services: time services, location services, software updates, on and on and on.

    It would be very difficult for a person to notice a low level bot doing something amiss. I have all the data, and I don't know how to do it.