vulnwatch
[Top] [All Lists]

Re: Php Nuke POST XSS on steroids

To: ascii <info@plot.uz>
Subject: Re: Php Nuke POST XSS on steroids
From: Paul Laudanski <paul@castlecops.com>
Date: Tue, 13 Mar 2007 17:59:37 -0400
Cc: full-disclosure@lists.grok.org.uk, news@securiteam.com, vulnwatch@vulnwatch.org, bugtraq@securityfocus.com, vuln@security.nnov.ru, webappsec@lists.owasp.org, Stefano Di Paola <stefano.dipaola@wisec.it>
Delivered-to: sp-com-lists@consult.net
Delivered-to: bugtraq-list@securepoint.com
Delivered-to: mailing list bugtraq@securityfocus.com
Delivered-to: moderator for bugtraq@securityfocus.com
In-reply-to: <45F48C77.5050406@katamail.com>
List-help: <mailto:bugtraq-help@securityfocus.com>
List-id: <bugtraq.list-id.securityfocus.com>
List-post: <mailto:bugtraq@securityfocus.com>
List-subscribe: <mailto:bugtraq-subscribe@securityfocus.com>
List-unsubscribe: <mailto:bugtraq-unsubscribe@securityfocus.com>
Mailing-list: contact bugtraq-help@securityfocus.com; run by ezmlm
Organization: CastleCops
References: <45F18BA5.50500@katamail.com> <45F4605E.7020203@castlecops.com> <45F48C77.5050406@katamail.com>
User-agent: Thunderbird 1.5.0.10 (Windows/20070221)
ascii wrote:
Paul Laudanski wrote:
I tried both your scripts at a few locations, and all I get back is this
[cut]

hi Paul, long time from ccc : )
Hey sure how are you?  Been well?  I've been really busy with CC.
it happens because http headers must be on a single line, it's a
formatting issue (my fault, i used to put a link to a plain text
version but this time i forgot about it), i've just created a txt
version of the advisory available here:

http://phpfi.com/214668
Thank you, this works.
it should be more usable, i dunno when the demos will stop working
on phpnuke.org so i've asked wisec to upload this video since www.ush.it
has bandwidth issues

http://www.wisec.it/ush/phpnukexss.html

obviously to bypass the anti-CSRF filter you have to mix the XSS with
the import_request_variables() trick (this doesn't work on phpnuke.org
because they have globals on, this is why i choose that domain)

consider that import_request_variables() will allows you to do much
more than an XSS, this is just an example advisory on an example product

I'd be curious to see your POC using the import_request_variables, because at the moment:

<br><center><a href="modules.php?name=Downloads"><img src="modules/Downloads/images/down-logo.gif" border="0" alt=""></a><br><br>
d4
<form action="modules.php?name=Downloads&amp;d_op=search&amp;query=token<>token

" method="post"><font class="content"><input type="text" size="25" name="query"> <input type="submit" value="Search"></font></form>
18
<font class="content">[

I'm not sure how this will have any effect as you must POST the data. In that sense, you can't exactly exploit a web user -- which is what you basically said with a gateway page. In a sense, you are setting up a sort of 'phish' against the site itself. For years we've been seeing to disable register_globals, and your workaround to enable it imvho is not a workaround at all. That shouldn't even be suggested.

In closing, can you supply an import_request_variables POC?

Thanks as always,
Paul Laudanski
http://www.linkedin.com/pub/1/49a/17b

<Prev in Thread] Current Thread [Next in Thread>