Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Convicted VoIP Hacker Robert Moore Speaks

Posted by ScuttleMonkey on Wed Sep 26, 2007 05:35 PM
from the kind-of-thing-an-idiot-would-have-on-his-luggage dept.
An anonymous reader writes "Convicted hacker Robert Moore, who will report to federal prison this week, gives his version of 'How I Did It' to InformationWeek. Breaking into 15 telecom companies and hundreds of corporations was so easy because most routers are configured with default passwords. "It's so easy a caveman can do it," Moore said. He scanned more than 6 million computers just between June and October of 2005, running 6 million scans on AT&T's network alone. 'You would not believe the number of routers that had "admin" or "Cisco0" as passwords on them,' Moore said. 'We could get full access to a Cisco box with enabled access so you can do whatever you want to the box. We also targeted Mera, a Web-based switch. It turns any computer basically into a switch so you could do the calls through it. We found the default password for it. We would take that and I'd write a scanner for Mera boxes and we'd run the password against it to try to log in, and basically we could get in almost every time. Then we'd have all sorts of information, basically the whole database, right at our fingertips.'"
+ -
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by camperdave (969942) on Wednesday September 26 2007, @05:38PM (#20761525) Journal
    It's so easy a caveman can do it

    So, not only do cavemen work in video production, they do network admin?
  • by Stormwatch (703920) <rodrigogirao@hotma i l . com> on Wednesday September 26 2007, @05:41PM (#20761565) Homepage
    "So the combination is one, two, three, four, five? That's the stupidest combination I've ever heard in my life! The kind of thing an idiot would have on his luggage!"
  • Well (Score:5, Insightful)

    by El Lobo (994537) on Wednesday September 26 2007, @05:42PM (#20761577)
    Once again, the weakest link in security is often NOT the software (which could also have problems). The weakest link is often the user: leaving the default password of a router, not activating encryption for wireless networks, using the same ID and password.... And , no, don't try to educate the masses. I have tries as an administrator of a large network. They never learn. Or they learn and the next day, they change their password to "qwerty" back again.
    • Re:Well (Score:4, Informative)

      by Joe The Dragon (967727) on Wednesday September 26 2007, @05:48PM (#20761641)
      In XP the default blank password does not let you do remote logins so it is some times more gives you more security.
        • Re:Here's one I do (Score:5, Interesting)

          by Destoo (530123) <destoo AT gmail DOT com> on Wednesday September 26 2007, @07:46PM (#20762539) Homepage Journal
          Why would they care, if it just works?

          I think I had 5 routers in my neighborhood on channel 6, with default passwords.
          I logged on into each and switched them to different channels.
            • Re: (Score:3, Insightful)

              I hope none of them intentionally wanted their router set that way.

              I should hope if they are knowledgeable enough to want their router configured that way they would also know to change the password from the default.

    • Re:Well (Score:5, Insightful)

      by Timmmm (636430) on Wednesday September 26 2007, @06:12PM (#20761861)
      It *is* a problem with the software. The software is designed for use by *people*. People who may not remember to change the default password.

      Easy solution - disable the product until the password is changed and intercept http connections so you can give people a helpful page saying "The default password is 'password'. This must be changed before this router/switch can be used. Click [here] to do so."

      I fail to see any flaws with this solution. Also read 'The Design of Everyday Things'.
      • ***I fail to see any flaws with this solution. Also read 'The Design of Everyday Things'.***

        I suppose that you probably don't. So let me help you out. The first problem you are going to encounter is that something like 15-20% of the customers are goijng to take an utterly irrational "It's MY router. How about you clowns let ME determine how to configure it?" attitude The second is that quite possibly a small percentage of them will actually need to run with default passwords. You can't imagine why.

        • Re:Well (Score:4, Insightful)

          by nuzak (959558) on Wednesday September 26 2007, @07:04PM (#20762259) Journal
          It won't feel like you're shoving policy down their throats if you don't have a default password at all, but make it so that it won't function until you complete the setup, which involves setting a password.

          Considering that you get folks like SAC who set the PAL codes for all their nukes to 00000, yeah there will always be people that bypass it. But at least won't be because nobody touched it at all -- someone had to run the setup. And when users get cranky and bypass it, then it's now 100% their problem. Especially when the SOX auditors come knocking.

      • Presumably these devices don't route packets, handle VoIP calls, etc. until you've at least put in basic network settings anyway. Seems like all you really need to do is make the device ask you to set an initial password as the very first step in the setup process.... It isn't rocket science. It's like when you get a UNIX account on some university box. They set an initial password based on your student ID/name/whatever. and the very first thing is a prompt that requires you to set a real password....

        • Re: (Score:3, Insightful)

          So we fix the users. I'm really sick of the prevailing attitude that "you're not going to change the users, so we have to accept this." Bullshit. In a civilized society, there must be consequences for stupidity.

          Users must be protected from themselves for the good of the whole. We don't allow people to drive 100MPH on the highway. We don't allow people to shout 'fire' in a crowded theater. What are people going to do, not use their computers? We're way past that point. The PC has become as important
    • No matter how much you educate, the user is the one piece in the equation that you can't 'fix', at least not on a large scale, which is why software and hardware *must be* designed in such a way that it works in a secure way even with a 'broken' user. The default password thing is easily fixed: don't set the same default one for each device, instead use a random one or none at all if possible (i.e. disable remote login). You don't want users to use 'qwerty' password, so use a function to check that the user
    • Re: (Score:3, Interesting)

      The weakest link is often the user: leaving the default password of a router,

      Are you sure it's the user?

      So, let me ask you this - why is the default password on routers all the same? Why isn't it different for each unit, and imprinted on the box or something? Such a trivial thing to do, yet it would do so, so much for improving security, and would have a trivial effect on usability.

      Routers are security devices. Other security devices (such as bike locks) have the default being rather secure, why can't route
  • by User 956 (568564) on Wednesday September 26 2007, @05:42PM (#20761581) Homepage
    Convicted hacker Robert Moore, who will report to federal prison this week

    Apparently Moore's law isn't quite up to snuff.
  • Random passwords (Score:4, Interesting)

    by MobyDisk (75490) on Wednesday September 26 2007, @05:47PM (#20761623) Homepage
    It doesn't seem too hard to ship the routers with random passwords. Is it just cheaper to not bother? Just thinking here...
    - They must run a test suite before shipping them so it should be easy to make that tool generate a random password and assign it to the router
    - You would have to print it on the router, or on a slip of paper
    - If it is printed on the router itself then you could make the router's reset button go back to that password, instead of Cisco0.

    Even if you don't implement that last bullet, it still seems like it would help a lot.
    • This moves the burden to the hardware manufacturer. What if this was the case, and network administrators (even good ones) the world over immediately assumed that everything they purchased out of the box was secure - right before a provider had a disgruntled employee upload the default password list for thousands/millions of routers to the internets? ... although that is just the FUD part of my brain talking. I actually like this idea.
      • If you argue that way you can never feel safe, since who says that there isn't a hidden backdoor in your otherwise secured router?
    • Re: (Score:3, Insightful)

      They must run a test suite before shipping them...

      No, they mustn't. Frequently, if your production QA is good you don't do 100% testing before shipping. Random sampling is usually good enough and significantly cheaper. I can't speak to any specific router manufacturer, but this is SOP in manufacturing.
      • Re: (Score:3, Interesting)

        Every device with an Ethernet interface has a 48-bit unique identifier built in. All such devices, in my experience, also have a sticker that displays their Ethernet address. Would it be so difficult to include, at manufacturing time, a small ROM that contained an initial password, unique to each device, and also displayed on a sticker? The additional cost of such a feature needs to be weighed against the additional security provided, but I think in some markets it would be a definite win.

        The manufactu

        • Keep in mind, the first half of that 48-bits isn't unique, it identifies the vendor. And they really aren't globally unique, but I'm not sure they have to be.

          Either way, this is going about it the long way. The simple solution is to make it so you have to change the default password the first time you config the device. Feel free to leave it "admin" from the factory, as long as it can't be "admin" after it gets configured.
    • Re: (Score:2, Interesting)

      I just received a modem/router from Verizon for DSL access and they had wireless access preset to a "random" SSID and WEP key which was printed on the modem. Of course, they then went and had the administration account be admin/password.
      • by Solra Bizna (716281) on Wednesday September 26 2007, @06:16PM (#20761897) Homepage Journal

        I just received a modem/router from Verizon for DSL access and they had wireless access preset to a "random" SSID and WEP key which was printed on the modem. Of course, they then went and had the administration account be admin/password.

        That's actually not so bad. In order to get on the wireless network to use the admin password in the first place, they would need to guess your SSID and WEP key. And everyone knows that's impossible, right?

        -:sigma.SB

        • Pretty sure any quality wireless router won't actually let you do wireless administration of the device. I know the Linksys box I have sitting on my desk requires you do be physically plugged in if you want to do any administration.
    • On Cisco wireless access points, the radio is disabled by default until you've either set a WEP key, or manually enabled the radio with no key set. It's not a great leap to make "commodity" routers that don't route until they've been given a new password.
    • Simple solution for ALL hardware: Default password requires you to have a local connection, or anything besides changing the password cannot be done using the default password. Using EITHER of these rules solves the default password problem. Anything that connects to a network should have one of these rules as part of the firmware. After all, it is common knowledge that around 80% of all hardware devices that contain a default password will never have it changed. Get your hands on a manual for the devic
    • It would have to imprinted upon the router in such a way that the password could not be easily rubbed off or otherwise made illegible. It would also add more cost than you might think to manufacturing of the router. It would probably be better to place a temporary sticker on the router with the default password printed on it and something along the lines of, "name of company strongly recommends that you change the admin password to something other than the default after configuring this router"
    • How difficult would it be to make the default something like the unit's serial number, then have the code require a change before even enabling network interfaces?
  • Ridiculous! (Score:3, Funny)

    by cromar (1103585) on Wednesday September 26 2007, @05:50PM (#20761659)
    You would not believe the number of routers that had "admin" or "Cisco0" as passwords on them...

    That's ridiculous. Everyone knows the most commonly used passwords are "love," "secret," and "sex." Oh and don't forget "God." It's that whole male ego thing.
  • Damn... (Score:4, Funny)

    by Cornflake917 (515940) on Wednesday September 26 2007, @06:02PM (#20761763) Homepage
    That caveman from the Geico commercials was just starting to make progress with his therapist. Let's hope the poor guy doesn't stumble upon this article. This hacker might get a few unexpected prison visits from whiny cavemen.
  • on the systems that I manage, no Web/telnet/ssh admin ports get opened to the outside world. If you want in, you'd better have a valid VPN key as well as a password, and VPN logs get checked regularly to prevent abuse. Good defence is multilayered.

    -b.

  • by SplatMan_DK (1035528) * on Wednesday September 26 2007, @06:09PM (#20761841) Homepage Journal
    Mjeah.

    So easy a caveman could do it.

    But apparently not so easy a caveman could avoid getting caught?

    What ever happened to the supercool hacking-thang called "not getting caught"?

    - Jesper
    • by lawpoop (604919) on Wednesday September 26 2007, @07:23PM (#20762381) Homepage Journal

      What ever happened to the supercool hacking-thang called "not getting caught"?
      I'm sure it happens all the time; it just never makes the news...

      It could even be happening right now...
      • So what you are saying is ...

        1.) Hack stuff using script-kiddie techniques
        2.) Keep at it until you are caught
        3.) Tell everyone the story about you being an idiot who got caught
        4.) Do a month of jailtime
        5.) $$$!

        Is that the kind of people who programmed my personal firewall and my anti virus app.?

        (Pleeeease, say "no", pleeeease, pretty-please)

        - Jesper
  • by rgaginol (950787) on Wednesday September 26 2007, @07:01PM (#20762241)
    Having these flaws present in a secure system, even for small companies is almost bordering on negligence. It takes 20 seconds to change a password, and god forbid if you've got too many to remember, write it down somewhere and store it in the company safe.

    The REAL problem I see with IT is a combination of inept administrators and an abundance of managers who don't understand the significance of things like this. A mistake like this not only represents a failure of an IT worker, but poor oversight by their manager. I've seen an administrator hired who had no technical competence but was able to talk to the managers about cricket. He was then replaced with a person who was even worse when the first dumb admin did the IT thing and left after making a huge mess. And yeah, a year after I'd left, the second administrator, after purchasing a new Cisco router with zero scoping calls me up and asks, "How do I install a Cisco router".

    There are books out there like "The practice of system and network administration", they help new administrators immeasurably, but so many just don't give a damn. There needs to be more incentive to have serious consequences for sloppy work. If we're ever going to be taken seriously, we need to find and flog administrators who set up a production router/firewall with a default password.
    • by Anonymous Coward on Wednesday September 26 2007, @09:26PM (#20763197)
      None. Imagine you have 80,000 switches, routers and other network devices. Some are 15 years old. Some are older and don't allow the password to be changed at all. You have hundreds of network admin folks spread all over the world.

      Now imagine that you want to change the passwords. You can't bring the network down or impact any current work. Networks of this size are constantly being modified. New devices added, routes being updated/refreshed. Redundancy deployed or a failure causing it to be exercised.

      AND you are a business - the people making decisions don't know anything about security - the only question is "what will all this work do to make more money?" Nothing? Then don't do it.

      Tracking 80,000 passwords isn't easy. During emergencies - your phone won't ring - your mother with a pace maker needs 911, not having access to the password in a switch that needs to be reconfigured manually isn't a good excuse.

      Ok, 1 of those hundreds of people leave the company. Do you change all the passwords ... again? Next week or the week after, someone else leaves/retires. Change again? Routers don't have per user accounts, do they?

      I've never seen a switch or router guy that wasn't overworked. Just like security folks.

      Anyway, just a few thoughts. It is never as simple as it seems.

      BTW, I worked at the big telecom company that wasn't hacked. I've since moved to a different telecom that is constantly being hacked and in the news for it. Until a few months ago, they had laughable security standards that seemed left over from 1990 to me and a flat network. Simply stupid, but being secure is a huge undertaking that isn't just network security, as you know. Only security failures get Executive attention, sadly.
  • " Alan Paller, director of research at the SANS Institute, says it's not the companies' fault. He even says it's not IT's fault. The problem, he says, lies with the vendors."

    I don't think so Alan. The means is there for an able bodied person to setup appropriate credentials within a few minutes. Most of these stupid logins are web based anyway. You click "Admin" and then "Change Password" and things are a lot better than they were a couple minutes ago. The biggest problem is unskilled technical people in po
  • by kilodelta (843627) on Wednesday September 26 2007, @10:39PM (#20763715)
    When you setup any new networking gear what is the very first thing you do? I can tell you what mine is, I change usernames and passwords. I even use strong passwords just in case.

    Nice to know telecom companies don't have a clue.
    • HP does this on their servers with ILO. The ILO password is a variation of the host name and random alphanumeric characters. Sadly, they don't do this with their procurve line of switches.
      • The ILO password is a variation of the host name and random alphanumeric characters.

        That's pretty hard considering the host name isn't assigned until the OS is installed. ;-) It's usually the host serial number plus some alphanumerics, but either way it's unique and is printed on a (removable) tag attached to the server.
    • Better yet: Why not have a unique default password that's printed on the device, or a function of a unique number that's printed on the device and NOT accessible from the network?

      That way the bad guy would need physical access to the particular box to read that label to get what he needs to construct the default password. (Since it's a default password the "view the label" hole could be instantly plugged just by changing it.)

      (Not from the MAC address, of course, nor the serial number if that's available i
    • I believe he more or less falls into the category of a "researcher". You probably could write a master's thesis on the password data/statistics alone!
    • by Ungrounded Lightning (62228) on Wednesday September 26 2007, @07:06PM (#20762291) Journal
      this guy should be congratulated for uncovering such slack security.

      If he told the owner about the insecurity and didn't exploit it himself, yes.

      imagine what havoc he could have made if he had been malicious, or had sold the passwords to Osama....

      Or if he kept it quiet and exploited it himself - stealing services and running up bills for the victimized system owners, building a business on it and pocketing money for himself and his co-conspirators.

      Wait... That's what he did, isn't it?

      No, he should not be congratulated. He should be convicted and punished as the thief he is.

      Wait... That's what happened, isn't it?

      Isn't it nice