mailing list archives
Re: Persistent XSS and CSRF on network appliance [subject corrected :) ]
From: "Joey Mengele" <joey.mengele () hushmail com>
Date: Wed, 27 Jun 2007 17:03:48 -0400
After plugging this hash into John The Ripper, I was able to
reproduce the text of the original advisory. It follows in
entirety. For those wishing to verify the hash provided by the
architect, I have also included the advisory in attachment form as
a convenience for the skeptics who say MD5 can not be reversed.
___ BEGIN LAME CRACKED ADVISORY ___
Persistent XSS and CSRF and on Wireless-G ADSL Gateway with
== Date found ==
24 June 2007
== Firmware Version ==
== Description ==
There are several persistent XSS vulnerabilities on the
to any of the vulnerable parameters:
The vulnerable (non-sanitized) parameters are the following:
Additionally, all HTTP requests are not tokenized using non-
Thus, all requests to the router's HTTP interface are vulnerable to
Request Forgeries (CSRF), perhaps by design.
The following is an example of a HTTP request (notice the lack of
POST /setup.cgi HTTP/1.1
Authorization: Basic YWRtaW46YWRtaW4=
Although the original request is a POST, we can convert it to a
GET, so that all posted parameters can be submitted on a single URL.
For example, the previous POST request can be converted to a URL
such as the following:
http://admin:admin () 192 168 1 1/setup.cgi?mtenRestore=Restore+Factor
By forging administrative requests ("Administration" button on the
router's HTML menu), an attacker can compromise the router provided
victim user visits a malicious URL or HTML page.
The attack can only be successfuly if any of the following
conditions are met:
- the administrator hasn't changed the default credentials
- the administrator's browser has an active authentication session
with the router's interface when the attack happens
== Persistent XSS PoC ==
The following URL creates a DoS condition by making the
"Administration" page inaccessible since 'history.back()'
will run everytime the Administration page is visited. Thus the
administrator won't be able to ever change the
default credentials unless a hard reset is performed on using the
router's physical "restart" switch:
http://admin:admin () 192 168 1 1/setup.cgi?user_list=1&sysname=admin&
== CSRF PoC ==
The following HTML page does the following:
- adds an *additional* administrative account, with a username
equals to 'attacker' and a password equals to '0wned' (without
removing original admin account!)
- enables remote HTTP management over port 1337
- sets other settings that are inrelevant to this discussion
// send 2 requests to add an administrative account and enable
// tries with default credentials and with credentials cached by
browser (if any)
var img = new Image();
var img2 = new Image();
'http://admin:admin () 192 168 1 1/setup.cgi?user_list=8&sysname=attack
The first URL forges the administrative request using the default
credentials, so it won't work if default credentials
have been changed.
The second URL doesn't specify any credentials as an attempt to use
the browser's cached credentials.
If the admin user has clicked on "Save password" on the basic
authentication prompt, most browsers will
prompt the user to confirm submitting the cached credentials. The
only situation in which browsers won't
ask the user to confirm submitting the credentials would be if the
malicious CSRF page was visited while
the browser has an active authenticated session with the router's
HTTP interface (very unlikely).
== Additional notes ==
- router reboots after saving settings (requests sent to
- all attacks were tested using Internet Explorer 7
- No firmware updates were available at time of testing, only GPL
code is available:
== References ==
== Credits ==
pagvac [ikwt.com] and Petko Petkov [gnucitizen.org]
___ END LAME CRACKED ADVISORY ___
On Wed, 27 Jun 2007 16:29:43 -0400 pagvac
<unknown.pentester () gmail com> wrote:
The file "research.txt" will be provided once the vendor fixes the
issues. At that point anyone can check that the hash matches the
included in this post.
Joey Mengele wrote:
Please provide the original content of research.txt so I can
that the hash is correct. I will also need the hash of your
On Wed, 27 Jun 2007 16:02:16 -0400 pagvac
<unknown.pentester () gmail com> wrote:
The HTTP interface of a network appliance has been researched
found to be vulnerable to several persistent XSS and CSRF.
Such research was done by pdp (architect) and myself. We
vendor and will publish the details when a fix is available.
The following is the MD5 hash for the advisory file.
$ md5sum.exe research.txt
Click here for to find products that will help grow your small
Click to compare & save $100's on medical insurance, free quote
Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia - http://secunia.com/
Re: Persistent XSS and CSRF on network appliance [subject corrected :) ] jt5944-27a (Jun 28)