Slashdot Mirror


Botnet Worm Targets DSL Modems and Routers

CoreDuo writes "The people who bring you the DroneBL DNS Blacklist services, while investigating an ongoing DDoS incident, have discovered a botnet composed of exploited DSL modems and routers. OpenWRT/DD-WRT devices all appear to be vulnerable. What makes this worm impressive is the sophisticated nature of the bot, and the potential damage it can do not only to an unknowing end user, but to small businesses using non-commercial Internet connections, and to the unknowing public taking advantage of free Wi-Fi services. The botnet is believed to have infected 100,000 hosts." A followup to the article notes that the bot's IRC control channel now claims that it has been shut down, though the ongoing DDoS attack on DroneBL suggests otherwise.

38 of 272 comments (clear)

  1. Tomato by Merritt.kr · · Score: 3, Interesting

    Glad I recently switched my router to Tomato. Works better than DD-WRT, too.

    --
    It is no measure of health to be well adjusted to a profoundly sick society. - Krishnamurti
    1. Re:Tomato by zombietangelo · · Score: 5, Informative
      TFA states:

      any linux mipsel routing device that has the router administration interface or sshd or telnetd in a DMZ, which has weak username/passwords (including openwrt/dd-wrt devices)

      This does not exclude Tomato, especially if your router is set up as mentioned or you have weak passwords.

    2. Re:Tomato by Repton · · Score: 5, Informative

      If you allow ssh access from the wide internet, and you have a weak password for root, you are probably still vulnerable..

      --
      Repton.
      They say that only an experienced wizard can do the tengu shuffle.
    3. Re:Tomato by Krizdo4 · · Score: 4, Informative

      Glad I recently switched my router to Tomato. Works better than DD-WRT, too.

      Why does this article make you glad you switched?
      The same thing that makes OpenWRT/DD-WRT vulnerable seems to be part of Tomato.

      FTFA
      "any linux mipsel routing device that has the router administration interface or sshd or telnetd in a DMZ, which has weak username/passwords (including openwrt/dd-wrt devices)."

      From Tomato Features list:
      "CLI (using BusyBox) with access via TELNET or SSH (using Dropbear)"

    4. Re:Tomato by John+Hasler · · Score: 3, Insightful

      > If you allow ssh access from the wide internet...

      Why would you do that?

      > ...and you have a weak password for root...

      Why would you do that?

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    5. Re:Tomato by Anonymous Coward · · Score: 5, Insightful

      If you allow SSH access from the wide internet and you allow passwords, you are probably still vulnerable.

      Really, just use SSH with private/public keys and you'll be okay.

    6. Re:Tomato by Yossarian45793 · · Score: 4, Insightful

      If you allow ssh access from the wide internet, and you have a weak password for root, you are probably still vulnerable.

      If you allow ssh access from the wide internet, and you have a weak password for root, you always were vulnerable. Now the vulnerability is just being exploited in a more automated way.

    7. Re:Tomato by xiong.chiamiov · · Score: 3, Informative

      You don't have to enable remote ssh access to manage your router, unless you really need to administrate it remotely.

    8. Re:Tomato by tobiasly · · Score: 3, Informative

      If you allow SSH access from the wide internet and you allow passwords, you are probably still vulnerable.

      Really, just use SSH with private/public keys and you'll be okay.

      Another alternative is to close port 22 and use a non-standard, high-numbered port instead. Not as secure but most automated attacks don't scan all 65536 ports looking for an open one. If I disable passwords I'm always afraid that the one time I really need to get into my LAN will be the one time I don't have my private keys with me.

    9. Re:Tomato by 644bd346996 · · Score: 3, Informative

      By default, Tomato doesn't allow remote (from WAN port) administration. I don't know about the other WRT firmwares, but Tomato at least is secure from this exploit by default.

    10. Re:Tomato by X0563511 · · Score: 3, Informative

      dd-wrt doesn't allow admin from WAN either, unless you tell it to.

      And you can tell it to do that intelligently, using SSH on a nonstandard port, enabling tunneling, and using public key auth.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    11. Re:Tomato by PReDiToR · · Score: 4, Informative

      > If you allow ssh access from the wide internet...

      Why would you do that?

      `ssh -i ~/.ssh/myrouter.key root@my.router.ip '/usr/sbin/wol -i 192.168.0.255 00:11:22:33:44:55'`

      But there is no reason on earth to use SSH with password authentication. Ever.

      4096bit keys with 30+ character passphrase is my standard at the moment.

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    12. Re:Tomato by Kadin2048 · · Score: 4, Interesting

      That would be nice, but it is not easy to do. The Linux distros that run on embedded routers are mostly set up to have only a single, root, user. DD-WRT is definitely this way, and I think Tomato is as well. It might be possible to rebuild it with multiple users but that is definitely not how it's designed right now.

      Personally what I'd recommend is not having any of the router's management interfaces exposed to the WAN side of things, for any reason, ever. If you think you might need to administer the router remotely, set up a hardened system inside the LAN somewhere, forward a nonstandard port to sshd on it, and then log into that machine and do SOCKS port-forwarding to connect to the router. This is how I run my home network and it takes literally only a second or two longer to connect to the router this way, versus if I had it directly accessible.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    13. Re:Tomato by Runaway1956 · · Score: 3, Insightful

      I have a very strong password. "Administrator" See? Twelve letters. I'm pretty sure that Microsoft assured me years ago that a twelve letter password made for a real strong hash......

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
  2. Tomato by Anonymous Coward · · Score: 3, Funny

    Don't forget, Tomatoes get worms too!

  3. What to do about it? by GrahamCox · · Score: 5, Insightful

    A. How do we know whether our kit is vulnerable?
    B. How to tell whether we are infected?
    C. What to do about it if we are?

    I'd guess most people, even geeks, just think of their router as a black box and don't know much about them as long as they keep on working.

    1. Re:What to do about it? by adolf · · Score: 5, Informative

      A. Is your password "admin," "root," "password," or some other such simplistic shit? Can you log into it remotely? If so, you're vulnerable.
      B. Does SSH still connect? Can you get to your router's web page? If so, it's not infected.
      C. It's a router, not something of any great intrinsic value. Nuke the firmware and start over. (Reset, boot_wait, JTAG - lots of ways to nuke a new firmware into these things without having network access to them. Listed previously are some good terms to Google for.)

      I'd guess that most people, even geeks, don't run dd-wrt, tomato, or openwrt on their router unless they've got a pretty good clue about what's going on.

      On the other hand: The average Joe, who just buys a WRT54G (aka: black box) from Wal-Mart, plugs it into his cable modem, and logs into the "linksys" SSID from his laptop isn't affected by this worm, since the default configuration doesn't allow remote access from the Internet at all.

    2. Re:What to do about it? by John+Hasler · · Score: 5, Funny

      > ...the default configuration doesn't allow remote access from the Internet at all.

      True. The crackers have to use the bot that controls his pc and the default password that he didn't change.

      --
      Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
    3. Re:What to do about it? by seanadams.com · · Score: 5, Insightful

      The average Joe, who just buys a WRT54G (aka: black box) from Wal-Mart, plugs it into his cable modem, and logs into the "linksys" SSID from his laptop isn't affected by this worm, since the default configuration doesn't allow remote access from the Internet at all.

      But it does allow access from the LAN side, so all that takes is one owned client connecting to that AP. It could even spread via laptops physically roaming to different hotspots (maybe not AT&T etc, but think of an independent coffee shop owner who should not have to be a networking guru).

      Routers seem like a nice prize indeed. Always connected and on a public IP, and there's millions of them!. I'm surprised it's taken this long.

      It's hard enough for most people to just hook one of these up, much less wipe a rootkit from it.

    4. Re:What to do about it? by chill · · Score: 5, Interesting

      I'd guess that most people, even geeks, don't run dd-wrt, tomato, or openwrt on their router unless they've got a pretty good clue about what's going on.

      Really?

      1. The article claims between 80,000 - 100,000 infected routers.
      2. Neither DD-WRT nor OpenWRT allow connections from the outside world by default.
      3. The worm brute-forces passwords.

      From this we can conclude that there are at least 80-100K geeks who opened their connections to the outside world and used weak passwords. This does not sound like people with a "pretty good clue" to me.

      --
      Learning HOW to think is more important than learning WHAT to think.
  4. Re:Run to my openWRT router and look for.. what? by Repton · · Score: 3, Informative

    Considering that TFA says one of the things the bot does is lock you out, I suggest that if you can log in, you are fine :-)

    --
    Repton.
    They say that only an experienced wizard can do the tengu shuffle.
  5. Easy fix by Anonymous Coward · · Score: 5, Funny

    Not a big deal, you can just:

    ssh to your router
    ifconfig eth0 down

    All fixed, not vulnerable anymore.

  6. Scary Targets... by IonOtter · · Score: 3, Insightful

    Okay, now this is scary.

    Folks having OpenWRT/DD-WRT are usually a bit more savvy that the average user, so to see something specifically targeting such users is surprising.

    And the fact it's gone this long without being noticed is even MORE frightening.

    --
    [End Of Line]
    1. Re:Scary Targets... by Techman83 · · Score: 5, Insightful
      TFA:

      any linux mipsel routing device that has the router administration interface or sshd or telnetd in a DMZ, which has weak username/passwords (including openwrt/dd-wrt devices).

      Anyone Savvy enough to want to run OpenWRT/DD-WRT should hopefully be savvy enough to have a decent password. I'm guessing by DMZ it means open slather access to the device. Open Slather + Weak Password = Your Own Stupidity

      --
      # cat /dev/mem | strings | grep -i cat
      Damn, my RAM is full of cats. MEOW!!
  7. Admin interface open on the WAN side? by Mondo1287 · · Score: 5, Interesting

    Who has their router set to allow access to the admin interface from the wan side? This is certainly not done by default. Is there some sort of browser hijack involved with this to gain access to the inside of the network?

  8. Re:How Can I Determine If My D-Link Router is Linu by The_PHP_Jedi · · Score: 5, Informative

    The subject text box isn't the "write-the-beginning-of-the-message-until-space-runs-out-and-then-use-the-big-textarea-under-it" field. The big textarea under it is there for a clear reason.

    Just sayin'.

  9. Needs more detail by lordtoran · · Score: 5, Interesting

    Ok, TFA states

    Get a shell on the vulnerable device (methods vary).

    How will this supposed worm manage to login to the box? Brute force? Properly configured Linux will block login attempts for quite a while after several failures. SSH? Can't be compromised within a reasonable time. Telnet? Not supported on all routers I know.

    The article doesn't go into the essential details, so I call FUD until proven otherwise.

    --
    Want to hear the voice of GOD? cat /boot/vmlinuz > /dev/dsp
    1. Re:Needs more detail by pushing-robot · · Score: 5, Insightful

      1. Be granted root access to the vulnerable device.

      2. Do something nasty.

      describes 99% of *nix (Linux, BSD, OS X) "exploits" I've seen.

      Some of it is intentional FUD, but it's still a good example of why users should be forced to learn exactly what programs are allowed to do with user and root/admin privileges.

      Most folks still think of programs the way they think of physical gadgets. Users don't understand privileges, and assume that programs are by nature isolated from each other, the operating system, and the user's personal files.

      It doesn't occur to them that a malfunctioning toaster could suddenly delete their car.

      --
      How can I believe you when you tell me what I don't want to hear?
  10. Old news to me by GaryOlson · · Score: 3, Insightful

    I commented on this exact subject about 18 months ago. Amused to see the security industry finally catching up.

    --
    Every mans' island needs an ocean; choose your ocean carefully.
  11. And you really needed to... by m6ack · · Score: 4, Interesting

    ... administer your home router over the Internet? Who does that? If you don't have an open port, even on these boxen, how could you be attacked?

    But, it seems to me that this is more likely an attack on stock Linksys boxen that re-flashes with a special DD-WRT designed to "phone home." Yes, DD-WRT/OpenWRT are also vulnerable if they have weak passwords, but the bulk is more likely the former.

    (Disclaimer: My home router runs HyperWRT & is not listed in DroneBL.)

  12. OpenWRT/DD-WRT devices all appear to be vulnerable by xmff · · Score: 5, Insightful

    How so? At least on OpenWrt, SSH and Webif aren't even exposed to the wan side without manually changing the iptables rules first.

    I guess it's the same on DD-Wrt.

    The devices that were targetted appear to have some serious flaws, here's a cite from an analysis of the malware:

    "Several revisions of the NB5 modem shipped with a flaw which meant that the web configuration interface was visible from the WAN side, accepting connections and allowing users to administer the modem using the default username and password of 'admin' from outside the LAN. Furthermore, some of these modems suffered from another flaw, meaning that by default, authentication was not enabled for the web interface - meaning no username or password was required."

    It really boils down to the usual find-weak-logins style of attacks, only the target platform has changed.

  13. Re:Preventative workaround by ristretto_dreams · · Score: 3, Informative

    errr, yeah, if you want to kill an ant with a nuke.

    Or just change your password from the default and set ssh/web/telnet administration to local segment only.

    Did you read the article?

  14. Wait Till They Get Verizon Routers Rooted by darkmeridian · · Score: 3, Informative

    The modem/router that Verizon provided for their DSL service had the firmware remotely upgraded. There is no way to avoid these updates. I hope it is secure. If someone roots that process, it will be the mother of all DDOS attacks.

    --
    A NYC lawyer blogs. http://www.chuangblog.com/
  15. Re:Run to my openWRT router and look for.. what? by KillzoneNET · · Score: 5, Informative

    Apparently I'm one of the "100,000" that got infected by this botnet.

    This morning my router would not connect to any websites, yet my modem when directly connected to my PC still did. I reseted the settings to default, disabled the vulnerabilities that got the idiots in and put a stronger 35 character username and password.

    How did I get infected in the first place? I left on remote access. And possibly my username and password weren't that complex. Live and learn I guess.

  16. Re:Hackers. by Anonymous Coward · · Score: 3, Funny

    You see, corn was very important in Japanese culture as it was originally from Japan, although an American Indian raid stole all plants and took them to America.
    However, after they met Americans which are greasy and yellowy white just like popcorn, they stopped eating it altogether.
    They put it over pizza so that the Yakuza can torture its victims. Japanese people are so scared of becoming fat like Americans that they would rather commit Hairy Curry also known as Sailor Fuku than eating corn pizza.

  17. Re:Hackers. by turing_m · · Score: 5, Funny

    Sex is like pizza... Even when it is bad, it's still pizza.

    The difference is... when you get desperate enough to eat disgustingly bad pizza, your friends won't bring it up for the next ten years at every possible occasion.

    --
    If I have seen further it is by stealing the Intellectual Property of giants.
  18. Re:Hackers. by machine321 · · Score: 4, Funny

    Some sex crust is so bad it's inedible too.

  19. Re:Hackers. by laejoh · · Score: 3, Interesting

    That's what she said :(