Slashdot Mirror


Linksys WiFi Gateway Remote Attack Risk Discovered

Glenn Fleishman writes "According to InternetNews.com, a tech consultant discovered that even if you turn the remote administration feature off on a Linksys WRT54G -- the single bestselling Wi-Fi device in the world -- you can still remotely access it through ports 80 and 443. Linksys sets the HTTP username to nothing and password to 'admin' on all of its devices by default. Web site scanning from anywhere in the world to devices that have routable Internet-facing addresses would allow script kiddie remote access, at which point you could flash the unit with new firmware, extract the WEP or WPA key, or just mess up someone's configuration and change the password."

68 of 311 comments (clear)

  1. Only 'moderately' critical ? by Space+cowboy · · Score: 5, Insightful
    Security consultants Secunia rates the flaw as "moderately critical" and urged users to configure a strong password for the administrative Web interface or restrict access to the interface altogether.


    Whereas I (owning one of these boxes) rate the flaw as a combination of 'wide open', 'come and hack me, here I am', and 'criminally stupid'. What the [insert expletive] is the point of the 'turn off remote administration' option, if it doesn't turn off remote administration ??!!

    I always make sure I enter my own password into every system of mine that lets me. At least that way it's only ever *my* mistakes that will trip me up...

    Simon

    --
    Physicists get Hadrons!
    1. Re:Only 'moderately' critical ? by VC · · Score: 4, Informative

      Its not that bad... The thing is a linux box, with an admin password.

      If you did the right thing and changed you admin password, then what you've really got is a linux box on a wan, with a hard to guess password.

      Besides which, your running the Sweadish firmware anyway arn't you. :-)

    2. Re:Only 'moderately' critical ? by SilentChris · · Score: 2, Informative

      It's only "moderately" critical (for now) because a simple hardware reset button fixes the problem. Once reset, go into the admin and set a bloody password -- problem never happens again.

      It would be more critical if the exploit permanently wrecked the router. As it is, most of them have their simple boot code in flashable ROM. Just grab the last good copy and work with it (if someone figures out a way to update the firmware to a bad version, well, then people are screwed).

    3. Re:Only 'moderately' critical ? by southpolesammy · · Score: 3, Informative

      Yes, this is only moderately critical because (a) the overwhelming majority of owners of these devices have them either directly or indirectly behind a NAT'ing cable modem or DSL connection, and (b) the "exploit" (if it can even be called that) is a known entity that any owner of one of these devices (myself included) should have realized the possibility of from day 1 and changed that password immediately, possibly before even connecting it to the cable modem.

      This doesn't rate a critical or severe like the script kiddies' worms that keep coming out because short of installing a custom firmware version, there's not much that can be done with the device once owned other than to screw with its owner's networking.

      --
      Rule #1 -- Politics always trumps technology.
    4. Re:Only 'moderately' critical ? by JHDrexler · · Score: 2, Informative

      I noticed this a couple of weeks ago on my router. I by-passed the issue by enabling port-forwarding and forwarded those two ports to a non-existant IP address. This solved my issue but YMMV. Hope it helps.

    5. Re:Only 'moderately' critical ? by Sancho · · Score: 2, Informative

      Actually, the article says WAN, not WLAN. WAN == Wide Area Network, meaning the Internet, which you are probably connected to if you have a device like this. WLAN == WireLess Area Network, I guess, and is the wireless part you're talking about.

    6. Re:Only 'moderately' critical ? by CharlieHedlin · · Score: 2, Interesting

      I am one of millions on a cable modem with no NAT other than what my gateway provides. Glad that gateway isn't one of these.

      I don't know what your experience is, but the vast majority of DSL and cable modem services I have used implement no NAT whatsoever.

  2. Ummmmm....... by Dr+Reducto · · Score: 4, Funny

    I am grabbing my laptop right now and going to my newfound open access point!

  3. psst ... by nick-less · · Score: 5, Funny

    don't tell to my neighbour...

    1. Re:psst ... by spoot · · Score: 3, Interesting

      Well, I just loaded my neighbors admin page on their linksys. Logged onto their non-wep wifi, loaded 192.168.1.1, and entered "admin" as the password. Bingo. Now I could screw with it if I wanted to, but that would just screw with my ability to use their network when I'm downloading pron on mine. It was all to easy. No scripting, no hacking, just obvious. I'll bet most (wi-fi) will be just like this. There are 3 wifi networks avaiilable from neighbors (homes) and none of them use wep or mac addresses.

    2. Re:psst ... by itwerx · · Score: 2, Informative

      Try doing it from the internet side...
      It works from the outside as well.
      This has actually been a problem for a long time. I first noticed it on one of their 802.11b series WAP/firewalls. I don't remember the model; it was an early one and died of over-heating a couple years ago, like most of their stuff does.
      (Tip for anybody w/a LinkSys WAP - put a fan on/in it!)
      Like somebody else commented, I just forwarded to ports to a bogus IP. I also sent a note to their tech support who told me to update to the latest firmware but that didn't help. I've seen it many times since on other models so it doesn't surprise me that even the latest and greatest is still wide open. :(

  4. All your gateways are belong to us by tedgyz · · Score: 4, Funny

    All your gateways are belong to us

    --
    "No matter where you go, there you are." -- Buckaroo Banzai
  5. Has nobody noticed these ports being wide open? by yebb · · Score: 4, Interesting

    Seems like a rather obvious issue, I'm suprised nobody noticed this before.

    1. Re:Has nobody noticed these ports being wide open? by CaptainSuperBoy · · Score: 2, Interesting

      I thought the same thing. There are literally hundreds of thousands of these things out there, and they've been on the market for probably 6 months at least. I'm assuming that not all of the WRT54G's are vulnerable.

  6. How is this different from normal? by Gothmolly · · Score: 5, Insightful

    Since 70%+ of the wireless users on my block do not activate WEP, or change the default channel, or use a non-default SSID, I'm willing to bet that nobody went through the effort to manually deactivate the admin interface, or change the password. You could argue that that is merely a de facto flaw, while the listed vulnerability is de jure, but from a practical perspective, this is no less secure than everything was anyway.

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:How is this different from normal? by ideatrack · · Score: 4, Insightful

      You could argue that, but seeing as there are decent sysadmins out there (no really) who will have turned this feature off, it's pretty severe. Admittedly if I had turned it off, then I'd check to see if that was actually the case, but it's very easy to just believe the interface. After all, they'll have checked it before shipping it, won't they? Won't they?

    2. Re:How is this different from normal? by blowdart · · Score: 2, Insightful
      this is no less secure than everything was anyway

      That's debatable. The admin pages are exposed to the internet at large by default, with a known username and password. Whereas with no WEP and so on you at least have to be physically close.

    3. Re:How is this different from normal? by mccalli · · Score: 5, Informative
      Unlike Netgear, Linksys routers have no way to stop broadcasting the SSID

      Mine does - I've got a "Wireless SSID Broadcast: Enable/Disable" option on the Wireless page. I'm running firmware 2.02.2

      Cheers,
      Ian

    4. Re:How is this different from normal? by fabs64 · · Score: 2, Interesting

      this always interests me how people from other countries talk of how WEP is never turned on. I'm from Australia and every ADSL wireless router or whatever that i have seen has WEP on by default and it comes with its own setup stuff on the cd that configures WEP without joe user even realising it. so what is the case with routers where you come from? do they just come with installation software that sets everything up automagically but for some insane reason doesn't configure WEP? or is joe user actually expected to set it all up himself and that's why WEP never gets done?

    5. Re:How is this different from normal? by Ath · · Score: 3, Informative

      You cannot disable the SSID broadcast on the Linksys WRT54G? Funny. When I change the radio button in the admin page to "Disable SSID Broadcast", it stops broadcasting the SSID.

      Please make sure you either clarify such statements or don't make them when they are false (as in the current situation).

    6. Re:How is this different from normal? by Kulaid982 · · Score: 2, Informative


      Linksys routers have no way to stop broadcasting the SSID
      Which Linksys WAP? The WRT54G certainly does allow you to turn off SSID broadcast, it's a setting under the "Wireless" tab on the administration page. When I first set up my wireless network, I initially left the SSID on to make it easier for me to verify that all my machines were within range and had good signal. Once satisfied, I turned off the SSID broadcast and took other steps to secure the network.

      Changing the default SSID doesn't help.
      I do agree with you here: the exploit we're discussing has nothing to do with the SSID broadcast, it deals with remote administration from the internet.

      --

      Isn't it interesting how you come to recognize posters based solely on their sigs???
    7. Re:How is this different from normal? by Sir+dies+alot · · Score: 2, Insightful

      I'm from the US and I've configured a few different routers, and from what I've seen, the majority of those come with an automagical cd that does not enable WEP, it just configures the network with the default SSID and the default username/password/port settings. One router specifically was by network everywhere, which you plugged in and attached to a modem and it was broadcast wirelessly, no setup, no cd, no nothing. You could just plug it in and let your wireless card detect the network. It was configurable, but Joe user wouldn't have the first clue as to how. Hope this helps.

      --
      The stupidity of your average American is just about the same as the average European, we simply show it off better.
    8. Re:How is this different from normal? by southpolesammy · · Score: 3, Informative

      This is so not true. My WRT54G has had an enable/disable toggle for SSID broadcasting included in the firmware since the day I purchased it about 18 months ago. Perhaps you're referring to an old version of firmware, but most anything purchased from Linksys since the WAP boom began has had this option.

      --
      Rule #1 -- Politics always trumps technology.
    9. Re:How is this different from normal? by mivok · · Score: 3, Informative

      Strange, thats exactly opposite to my experience - my linksys WRT54G can turn off SSID brodcast (and has WPA support incidentally), whereas the netgear access point (WG502) that I replaced with the linksys was pathetic with respect to security, providing only WEP (with a broken promise of upgrade to WPA), and not allowing me to hide the SSID.

  7. things like this... by fabs64 · · Score: 5, Insightful
    honestly these sort of completely blatant and downright dangerous security holes in software i think should pave the way for making developers culpable for damages incurred by defects in their software.

    I mean honestly, if a Surgeon said that they sewed up a hole in your stomach but really didn't they would be considered criminally negligent wouldn't they? How is a company allowed to release something as obviously dangerous as this to the public without having some sort of liability?

    1. Re:things like this... by jimicus · · Score: 3, Insightful

      Mod parent up as insightful... it's an excellent point.

      We sue architects for designing buildings which collapse before they're even completed. We sue car manufacturers who build cars which have an annoying tendency to explode. Our relatives sue doctors who say "that little lump is nothing to worry about". In each case, a person in a profession which requires a degree of understanding greater than expected of the general public has screwed up.

      I can only imagine that the IT industry has convinced the general public that computers are Just So Complicated that nobody on earth can possibly understand them properly, and therefore such mistakes are to be expected. One day someone will be killed because of such complacency. Perhaps then the industry will start to take some responsibility for its mistakes.

    2. Re:things like this... by gclef · · Score: 5, Insightful

      There's a concept called "fitness for purpose" that I think applies here. If you used bicycle tires on a car, for whatever reason (price being an obvious one), if you then got hurt in your car, you'd have no one to blame but yourself. Bike tires aren't fit for use on a car.

      By the same logic, if you used a cheap, home-user piece of crap for a life-critical operation, you deserve to be sued into oblivion, since it wasn't designed for something critical. Personal firewalls like this Linksys thing are not suited for life-critical use, and everyone who knows what the hell they're doing should realize that.

      If you use a piece of software that is sold as "fit for this purpose" (like, using windows-embedded health monitoring devices) and it fails due to a poor design, then you're right on...the vendor of that device should be sued.

    3. Re:things like this... by kfg · · Score: 2, Insightful

      When was the last time you saw someone firmware upgrade a building?

      My brother makes his living doing this.

      KFG

    4. Re:things like this... by jimicus · · Score: 2, Insightful

      Ah, great solution, "sue". Guess you must be American.

      I'm not. I'm English.

      Here in Merrie Olde England, a few years ago, the London Ambulance Service decided that a computer could work out the most efficient route from A to B through a busy city far better than a human controller. Reference Here

      Thus the computer could decide which ambulance was best placed to answer a specific call based on its geographic location far more efficiently than a person.

      It couldn't. People died. Nobody was ultimately held liable. Had the problem been that a bunch of vehicles with faulty steering was sold as ambulances, the manufacturer would have been feeling the pain for years.

      It is my 'umble, very 'umble opinion, that there are some things which we still do not understand sufficiently to turn into reliable computer systems. Oh, we understand them ourselves OK - regular drivers know where's a bad place to drive in their home town at rush hour - but we simply don't have a thorough enough understanding to be able to turn it into a reliable computer system. Yet we still try it.

    5. Re:things like this... by BoneFlower · · Score: 2, Interesting

      Bugs in software are inevitable... its a fact of life.

      The only chance of having a bug free system is one organization having control of the entire system from hardware design, to the firmware, to the OS, the support libraries, and the application software. In the current IT world, where your hardware consists of generic components from half a dozen manufacturers, your OS from someone else, and application software and support libraries from other companies, none of which have influence over each other and have minimal if any chance to look at the detailed design of the other components it has to work with... Bugs are simply unavoidable. They can be minimized, and the effects minimized further, but they simply cannot be prevented with enough reliability for liability lawsuits to be remotely fair. It simply is not possible.

      Which, of course, is why computers where human life is at stake should be designed as complete units, or at the very least all parties involved should have access to all the documentation and source code of the other parties involved, so they can really dig deep and make sure they don't trip up on "noone in their right mind would EVER send that data to this function".

  8. 2 points by millahtime · · Score: 4, Informative

    1) 90% of the people that buy these are your basic at home user. They don't ever change the default settings. It's just a setup and go. There are 5 such ones in my apartment alone in range of my apartment

    2) 99% of people aren't going to update the firmware when it comes out so this bug will be floating around for some time.

    The average joe 6 pack needs to be forced to use the security with it. If you give it as an option then it many times will be ignored. Security needs to be made part of the setup and updates need to be easy to install.

  9. port fowarding by Anonymous Coward · · Score: 4, Interesting

    What happens if you are fowarding port 80 to an internal box? Thats what I currently do. If i access my external ip I get my webpage, I can only get my routers admin page by using its internal IP.

    1. Re:port fowarding by mccalli · · Score: 5, Informative
      What happens if you are fowarding port 80 to an internal box?

      From the article:

      "As a workaround until a firmware upgrade is issued, Rateliff recommends the use of port forwarding send ports 80 and 443 to non-existent hosts. "Note that forwarding the ports to any hosts -- including listening ones if you are actually running servers -- will override the default behavior," he explained."

      So you're ok. As am I, or at least as I will be after I've just finished forwarding 443...

      Cheers,
      Ian

  10. in short by andy1307 · · Score: 2, Informative
    The problem is the default password: admin....?

    How does changing the default password help if you don't turn on WEP? Can't someone get on the network using the default SSID(linksys) and sniff for passwords?

  11. The reason the risk is "moderate" is... by Ath · · Score: 4, Insightful

    1) This problem is specific to one version of firmware. I can guarantee it has not been there in many of the versions I have used. 2) It only affects units that have not had their default password changed. I agree it is a security risk but it should be kept in perspective. If a user does not change the password, that is not a design problem of the firmware. The only real problem is that the function to turn off remote administration on the WAN port stopped working in the specific release of firmware. The article does not mention which version of firmware this guy was using, so we cannot confirm it. I personally use a modified version of the Linksys firmware, of which there are now quite a few.

    1. Re:The reason the risk is "moderate" is... by Ath · · Score: 4, Informative
      This problem is specific to one version of firmware.

      I should correct this because some people with the 2.02.07 version that this guy claimed to be using are reporting they cannot reproduce the problem.

      This could be basic user error. By the way, the remote admin function is disabled by default in the WRT54G firmware.

      What gets me is that if you want to bitch about the WRT54G firmware, there are plenty of better reasons than this apparently bogus one. Only the hacked firmwares really make this hardware shine (and have all functions plus new ones work properly).

  12. Firmware flash by thedillybar · · Score: 2, Interesting

    Recent articles show that this little thing is pretty powerful. What stops someone from flashing a box, running an open relay, ftp server, web server, or anything else of the sort (besides a strong, non-default password)? Just what we need is spambots on these damn Linksys routers..

  13. Bugtraq submission by mrgrey · · Score: 5, Informative


    Manufacturer: LinkSys (a division of Cisco)
    Product: Wireless-G Broadband Router
    Model: WRT54G
    Product Page:
    http://www.linksys.com/products/product.asp ?grid=3 3&scid=35&prid=601
    Firmware tested: v2.02.7

    In a recent client installation I discovered that even if the remote
    administration function is turned off, the WRT54G provides the
    administration web page to ports 80 and 443 on the WAN. The implications
    are obvious: out of the box the unit gives full access to its administration
    from the WAN using the default or, if the user even bothered to change it,
    an easily guessed password.

    I reported this to LinkSys (along with a number of other non-security
    related issues) on April 28. I received no reponse addressing this, and no
    updated firmware has yet appeared on their firmware page
    http://www.linksys.com/download/firmware.asp ?fwid= 201

    To work around this, you can use the port forwarding (irritatingly renamed
    to Games and whatever) to send ports 80 and 443 to non-existant hosts. Note
    that forwarding the ports to any hosts -- inluding listening ones if you are
    actually running servers -- will override the default behavior.

    On a personal note, there are a number of reasons for which I am thoroughly
    disappointed with LinkSys since the acquisition by Cisco. For the sake of
    what was once a rock-solid product and great brand name, I hope things
    change soon.

    --
    Alan W. Rateliff, II : RATELIFF.NET
    Independent Technology Consultant : alan2@rateliff.net
    (Office) 850/350-0260 : (Mobile) 850/559-0100

    [System Administration][IT Consulting][Computer Sales/Repair]

    --
    -Tolerate my intolerance
    1. Re:Bugtraq submission by bhmit1 · · Score: 2, Interesting

      This was followed up by multiple people saying it doesn't work. The most likely explination comes from Jason Munro who says:
      > Testing this issue with a recently purchased WRT54G here showed that while
      > I can access the web interface on the WAN IP from the LAN behind the
      > linksys, I can not access it from another location on the WAN side.

      Also, there were other replies saying that you could fix this by forwarding these ports to non-existant IP's if you were able to reproduce the issue.

  14. Well... by Rican · · Score: 5, Funny

    ...anyone dumb enough to leave the router with the default password deserves to be h4x0red. I assume that by now pretty much anyone that owns a computer knows the need to create their own password not only for their PC but other devices/peripherals.

    Although, I tried changing mine to "penis" and it returned a message saying: "Password is too small."

    Go figure...

  15. What if some script kiddie meshed them all? by Baldrson · · Score: 4, Interesting
    The 32M RAM version of the WRT54G has enough capacity to run the current release of MeshAP. The problem is booting it off of the 8M of flash that is available on the WRT54G. You could overcome this by incrementally reflashing them to boot from the mesh itself. This would fix the security hole too.

    Understand, I'm not advocating any kids actually do this -- its just a fun, if slightly whacked, idea.

    1. Re:What if some script kiddie meshed them all? by AKnightCowboy · · Score: 2, Funny
      Imagine what you could do with a Beowulf cluster of these...

      Wow, you could cluster 100 of these together and get the computing power of a Pentium III. Imagine what you could do with that kind of hardware.

  16. NOT by Merlin42 · · Score: 3, Informative

    I have one such router(HW revision 1.0, firmware 2.02.7) so I gave it a guick check (again ... I tested it when I bought it) and I can't get the remote administration page on the WAN. Currently, I only forward port 22 and I disabled the DMZ.

  17. Does it matter? by thedillybar · · Score: 2, Insightful
    even if you turn the remote administration feature off on a Linksys WRT54G

    Isn't it safe to say that if someone finds the "remote administration feature" and turns it off, they're also going to change the default password while they're in there? Or do people think oh, since you can't remotely administer this thing from outside, it doesn't matter? Sounds sketchy to me, I don't think it's going to be a big deal.

  18. Simple, simple solution by incog8723 · · Score: 2, Funny

    It has been my experience that if you use a combination of wireless and wired technology (ie, a carrier pigeon tied to a really long string so you can pull it back really fast--the cats really love to chase the carcass, but you'll get your data back without incident).

  19. Okay.... by s.a.m · · Score: 3, Insightful

    So whats the big deal here? If you change the password etc then the problem is solved right? Ohhh thats right you're talking about people not READING the damn manual telling them what they need to do!

    Well tell you what, tough. You didn't read, you didn't listen, then pay the consequences. It TELLS you that you need to change the password etc and what you should do. If you choose not to do it, then face the consequences.

    See a Red Light means stop, if you choose not to obey that and get in an accident and get hurt, well sorry but you pay the consequences of your actions.

    I hate being so negative sometimes but damn, there comes a time when even the Big red letters not the widespread panic across the news won't help.

    Yes, I agree, the companies should make these things where you have to create a new password and username etc, but there's only so much they can do. B/c we all know that most people would leave the password field blank. I know this all to well as the CEO of my company has a blank password on his personal email addy.

    1. Re:Okay.... by David+Byers · · Score: 2, Insightful

      We've known for years or even decades that people for whatever reason often won't change the default password of the default account.

      Saying "change the password" in the manual in no way absolves the manufacturer of the responsibility to provide reasonable default, especially when they know that many of their customers won't change that default.

      If you make a product for the mass market, design your product accordingly and make it easy for your customers to do the right thing and hard to do the wrong thing. Most people will take the path of least resistance. Make sure that path leads to a good place.

      Linksys could have done better. They could have required a password change before allowing the access point to accept outside connections. To combat bad passwords they could warn users them. They could even *generate* good passwords and encourage home users to tape a note of the password under the access point.

      And the fact that your CEO has a blank e-mail password does not imply that most people leave passwords blank. What we do know is that many people will choose weak passwords, but even weak passwords are better than blank defaults.

    2. Re:Okay.... by evel+aka+matt · · Score: 2, Insightful

      Fine, and it's Master's fault when I leave my front door unlocked and then get robbed. But, but, I had a sign on the gate that said "FRIENDS ONLY"!!!!! That's a lame damn excuse.

      I'll let you know when I find an intelligent user that says "fuck it, admin is fine, not like anyone else has access to it."

  20. does anyone know by millahtime · · Score: 3, Interesting

    does anyone know if these are the access points they use at all those starbucks?

    1. Re:does anyone know by darkain · · Score: 2, Insightful

      please keep in mind tho, that Cisco and Linksys ARE the same company now. how much further spread is this to their other products?

  21. Use Custom Linux firmware by Anonymous Coward · · Score: 2, Informative

    You can flash the firmware to one from sveasoft http://www.sveasoft.com and avoid the whole problem. You also get a nifty linux environ to work with.

  22. Additional info on WRT54G administration page by alanxyzzy · · Score: 5, Informative
    This BUGTRAQ article has some interesting observations made by the original reporter of this vulnerability.
    I have made the effort to grab three additional units, all v2 hardware, off-the-shelf, and here is what I have found: Two of three units came with the firewall enabled, while one of the three came with it disabled. The packaging leaves no evidence as to whether any of these items were previously opened and returned.

    Interestingly, all three units from local resalers came with v2.02.2 firmware, while the second unit from CDW I tested in March came with v2.02.7. BOTH of the units which came off-the-shelf with v2.02.7 behaved as previously described in my original notice; I do not have records of the firewall setting of the units from March, although they both did behave as predicted after a factory reset.

    I would like to assume that the one-of-three v2.02.2 firmware units which came with the firewall disabled was an anomoly, and possibly a customer return. Nicely, flashing these units to v2.02.7 retains all settings, including the firewall status.

    Now the catch. In v2.02.7 with the firewall disabled and remote admin turned off, the admin page becomes available on ports 80 and 443 on the WAN. This works whether the unit is in DHCP or PPPoE mode.

    Port State Service
    80/tcp open http
    443/tcp open https
    Remote operating system guess: Linux Kernel 2.4.0 - 2.5.20

    So part of the original notice is valid, with the exceptions noted. I don't have any more v2.02.2 units to test as they have all now been flashed with v2.02.7, I have no more unmolested v2.02.7, and I am out of petty funds to purchase more :)

    So, I will eat some crow on the original notice. To sum up, the admin page is most definitely available to the WAN if the firewall is disabled, regardless of the remote admin setting. And at best the potential for getting a unit off-the-shelf with this behavior is somewhat like an Easter egg hunt. I have received an even mix of responses positive and negative to the original notice, so others are reproducing this OTS.

    Some thoughts...

    It could be resonable that units which come v2.02.2 OTS then flash to v2.02.7 may not experience this behavior due to stored factory settings from original v2.02.2 system carried over to v2.02.7. That would explain the exception of the OTS behavior of the v2.02.7 units received in March.

    Now I am also aware that other LinkSys items I have received have come with firmwares not yet available on the website -- most recent example, a WPS54GU2 which came with firmware 6032 while only 6031 was available on the website. It may be more reasonable that since the firmware v2.02.7 is dated March 17, my order for the WRT54G was placed on March 23, maybe a pre-release of the firmware? I cannot imagine that there would be such a diverse distribution of this product direct from LinkSys?

  23. What a lot of worm flash food! by AndroidCat · · Score: 2, Interesting
    Just think of the havoc that a Linksys Flash worm would cause: a worm that searches out other vulnerable Linksys boxes, re-flashes them with the wormed software, and contines on while the offspring does likewise. Something like that would spread very rapidly and result in a lot of junked undead WiFi gateways.

    Anyone know of another WiFi gateway company that would be good to buy stock in? They might suddenly be getting a massive number of orders.

    --
    One line blog. I hear that they're called Twitters now.
  24. I don't think this is true by jridley · · Score: 2, Interesting

    I have one, as do several of my friends.

    Pretty much the first thing I did when I took mine out of the box was to try to access port 80 and 443. No go.

    After seeing this, we tried again. None of us can access the box from the WAN port, only the LAN side.

    I wonder if this guy got a refurb or one that had been returned to a store after a user screwed with it?

  25. There are backdoored firmware available. by acz · · Score: 5, Informative

    Most of slashdot readers already know that there are a bunch of modified firmwares for the wrt54g such as this one. You should also be aware to realise that they are already backdoored/rootkit version (custom version of teso's adore of the wrt54g which will hide specific clients, processes, mac address and connections. It should also be noted that vulnerable linksys access point are trivial to detect using kismet (runs on linux, *bsd, zaurus, wrt54g) or kismac (runs on Mac OS X).

  26. Serial number as username and password? by Pascal+Sartoretti · · Score: 5, Insightful

    A basic problem with factory settings are the well-known usernames and passwords. Why not simply set them to the device's serial number?

    1. Re:Serial number as username and password? by LincolnQ · · Score: 2, Insightful

      Probably because they print 50 billion ROM chips all identical, and it would be a significant cost to reprogram each one differently with the serial number.

  27. People have already died.... by afxgrin · · Score: 2, Informative

    There's several cases where software failure has been fatal.

    How about the case of the THERAC-25, where several died or were seriously injured.

    This is a typical case study shown in any ethics course involving software design. It turns out the cause of the severe radiation burns was from the operator entering commands and parameters faster than the unit could handle.

    Then there's the Soviet pipeline that blew up due to delibrately buggy software stolen from the US.

    Then there's the Osprey , had software bugs that killed 30 Marines in 3 accidents.

    There's also 2 commercial jet crashes due to software problems with either radar, or just reporting position properly to the pilot, killing over 300 people in the 2 accidents.

    This problem is very real. So when people joke about getting a BSOD while driving a car, it's highly plausable.

  28. Which doesn't matter if you use Windows XP by the_skywise · · Score: 3, Insightful
    Because Windows XP FORCES you to leave SSID on or suffer the wrath of not being able to connect if you have multiple wireless routers in the area.

    See Microsoft Link

    Microsoft even tells you that this is a "good thing" at the link:

    Disabling SSID broadcasts on an access point is not considered a valid method for securing a wireless network.

    1. Re:Which doesn't matter if you use Windows XP by tstiehm · · Score: 2, Insightful

      This isn't true. While XP won't detect a WAP with the SSID broadcast turned off, you can manually configure a connection to the router. This whole point of turning you SSID broadcast off is to not allow automatic detection of WAPs. I would say MS is working within the standard in this case.

      I have this specific situation, I am not broadcasting my SSID but I have 3-6 WAPs broadcasting SSIDs around me. I have no problem.

  29. not not .... well sorta by Merlin42 · · Score: 4, Informative

    Actually I was able to reproduce the 'problem' It is not mentioned in the article, but you can access the admin page from the WAN port if 'firewall protection' is disabled.

    In hind sight this sort of makes sense ... although it is NOT at all obvious at first glance.

    In any case I wouldn't consider this to be a HUGE problem since 'firewall protection' is on by default and 'Joe 6pack' is unlikely to turn it off since the general perception amoung nongeeks (at least in my experience) is that Firewalls are magical good things that block bad stuff (for varying definitions of bad).

    1. Re:not not .... well sorta by LoadWB · · Score: 2, Informative

      I tried two different units and both showed the same results. Even after resetting the units, I was able to hit port 80 and 443.

      However, as my follow-up says, and as no one else has mentioned, I bought three brand new units from local retailers, each came with v2.02.2, and they weren't vulnerable OOB, except for one that came with firewall off -- and I assume that had to be a customer return.

      However, in the end, if firewall IS disabled, it DOES work as described on newer units. I cannot explain why the first ones I got with v2.02.7 behaved this way without any configuration changes.

  30. Re:psst ... OFFTOPIC by digitalsushi · · Score: 3, Interesting

    I live in a mill building on both sides of a river. There's 310 apartments with about 700 to 1100 people, I guess. When I moved in during May 2003, there was 7 broadcasting wireless networks. When we renewed our lease this May, we warwalked it again and there were 22. Both times, about 60% were completely wide open, and about 75% of them were linksys devices. One fellow across the river must have a booster or something because his network punches through way too many walls. He would seem to be on the interior side, facing the river, and I can get him on the opposite side of his building, as well as into my own building on the opposite side of the river. My roommate's girlfriend lives down the hallway and she can see exactly 6 wireless networks. 3 are wide open.

    With people giving away USB 802.11b cards for free, the temptation to steal all that free interenet is just well, it's inevitable that it gets used.

    Oh, and we had this great idea! See, there's so many open wireless networks at our place, and so many people with open filesystem shares, that one of the things we do to make a little spare cash is that we use that unified network adapter linux has where you can bind interfaces together. It's a little sloppy but we effectively have an aggregate 12.0 megabit connection out, and 1.2 megabit connection in, from the internet over 4 wireless lans we connected to. Then we did some filesystem on a filesystem type things with the open file shares and made a psuedo RAID using the neighbor's unknowingly shared directories. We can sell 1.2 megabit webhosting for 12.95 a month with zero infrastucture costs. I guess if I had to describe it in a word I'd say that it's "sweet."

    --
    slashdot: where everyone yells sarcastic metaphors to themselves to understand the issue
  31. It's not a priority issue... by the_skywise · · Score: 2, Informative

    I thought the same thing. The problem I found is that XP will select based upon signal strength. In my case, I was at a friend's apartment. His router was in the next room, but his neighbor's router was immediately behind us next to the wall. So I could specify the non-SSID connection and have it at the top of the priority list, but it would eventually drop it in favor of the SSID one because it had a stronger signal strength.

  32. That, I hadn't tried... by the_skywise · · Score: 2, Interesting

    But in retrospect, my friend (who's apartment I had this trouble at) was using Windows 2000 and using a netgear wireless card's app and didn't have this problem... But we attributed it to Windows XP's new behavior over 2000... (which is sort of true...)
    I hadn't thought about using the linksys app... (which I had uninstalled because I didn't want all the icons cluttering up my start bar and, geez, Windows XP already provides those services anyway...)

  33. Re:Too Late -- Expired by digitalsushi · · Score: 2, Informative

    check it every now and then, if it's expired. it seems to cycle through after each expiration. i grabbed mine after the first time i saw it expire.

    http://www.pcmall.com/pcmall/shop/detail.asp?dpno= 345833&adcampaign=email,PWB02474

    there's a vendor that has it til june 30th. there's a ton of these, just google for "free usb wifi" or something.

    --
    slashdot: where everyone yells sarcastic metaphors to themselves to understand the issue
  34. Re:So it ONLY happens IF the FIREWALL is DISABLED by LoadWB · · Score: 2, Interesting

    It should, somewhat. At first I felt bad, like perhaps I *had* jumped the gun when I made my first report. Even after I went over my original notes, I still wasn't satisfied due to the fact that I was getting people who stated they could not reproduce this, while others said they could.

    So I put some more $$ into it and got three new ones. Sure as shit, it didn't work OTS, nor after flashing. So I spent some serious time trying to vindicate my original findings, which are now seemingly worthless.

    Because of that, I put out a follow-up as quickly as I could, detailing my experience with more recent hardware, admitting that results from the tests in March was indeed dated.

    Then today I see my name and my original post blasted around, as if I had never posted the follow up to clarify the whole affair. Word travels fast, huh!

    Cisco/LinkSys never got back to me to help with troubleshooting after I made the results of my testing available to them, the firmware version on the website never changed, and I had the results of two new units on which to base my report. Once I collected responses to my post, I made the effort to keep from looking like an ass, and also to try to figure out why and if this would be coming from LinkSys as-is.

    What it boils down to is that some people may be able to reproduce this behavior off the shelf with v2.02.7. Others will only see this behavior after disabling the firewall. The bug certainly exists, but it doesn't seem to be entirely LinkSys's fault if that behavior makes it to the home user.

  35. You think that's scary? by moyix · · Score: 2, Informative

    I've been following this on BugTraq. As others in this discussion have pointed out, it's not that big a deal, since most people turn the firewall on. There's also an interesting post about someone who bought a few of them and checked whether the firewall was enabled by default--it turns out that two of the three units he tested came with the firewall enabled.

    Much more terrifying, though, is the fact that Netgear WG602 Access Points have a default admin account that can't be turned off, with the username "super" and the password "5777364". So expect anyone on the WLAN/LAN to be able to own your router if you have this product and enable the admin interface.