[<prev] [next>] [day] [month] [year] [list]
Message-ID: <000a01c6bd74$8cd36cc0$0c93ad80@outreach.vt.edu>
Date: Fri, 11 Aug 2006 14:32:48 -0400
From: "TeamXMM Consulting, Inc." <security@...mxmm.com>
To: <ginsurabbit@...mail.com>, <bugtraq@...urityfocus.com>
Subject: RE: linksys WRT54g authentication bypass
Use a different Firmware then... Preferably, Sveasoft or DD-WRT
<quote>
The Sveasoft firmware is a replacement firmware upgrade for ASUS,
Belkin, Buffalotech, and Linksys wireless routers.
</quote>
:D
Sincerely,
TeamXMM Internet Security & Consulting, Inc.
Email: security@...mxmm.com
Web http://www.teamxmm.com
-----Original Message-----
From: Ginsu Rabbit [mailto:ginsurabbit@...mail.com]
Sent: Tuesday, August 08, 2006 2:21 PM
To: guant@...kermail.com
Cc: bugtraq@...urityfocus.com
Subject: Re: linksys WRT54g authentication bypass
>From: "guant a" <guant@...kermail.com>
> > I'm having some trouble believing this hasn't been reported before.
> > If
>you
> > have a linksys router handy, please check to see whether it is
>vulnerable to
> > this attack. It's possible that all of the linksys router web UIs
> > have
>the
> > same bug. Hopefully the problem is isolated to one particular model
> > or firmware revision.
>
>This is fixed in at least v4.00.7 and above. Your original command
>doesn't work, the file doesn't even exist. But redoing it as such:
>
>curl -d "submit_button=WL_WPATable" -d "change_action=gozila_cgi" -d \
>"submit_type=" -d "action=" -d "security_mode_last=" -d "wl_wep_last="
>-d \ "security_mode=disabled" http://192.168.1.1/apply.cgi
>
>Results in "Authentication Required". (The strings were grabbed from
>ethereal, as I disabled the security, which would explain the multitude
>of empty options, but whatever.) This is an old bug that was fixed,
>which should explain the lack of vendor dialog. Upgrade, upgrade,
>upgrade. :)
I wish I could upgrade. The latest firmware revsion for my router is
1.0.9.
Your router and mine may have the same name, but there the similarity
ends. Flip your router over to figure out which hardware revision you
have.
Mine is the v5. Yours is probably v4 or earlier.
I'm told that there was a major change in the router between v4 and v5.
v4 and earlier were based on linux. v5 and later were based on VxWorks.
Linksys appears to have introduced this bug when they made that switch.
Thanks for your testing.
--
GR
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
Powered by blists - more mailing lists