Sign Up for Your FREE Weekly SecurityTracker E-mail Alert Summary
|
|
|
|
|
|
|
Put SecurityTracker Vulnerability Alerts on Your Web Site -- It's Free!
|
|
|
|
Become a Partner and License Our Database or Notification Service
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PHP-Nuke Input Validation Holes in Feedback, Downloads, Journal, and Other Modules Permit Cross-Site Scripting Attacks
|
|
SecurityTracker Alert ID: 1009439
|
|
CVE Reference: GENERIC-MAP-NOMATCH
(Links to External Site)
|
Date: Mar 16 2004
|
Impact: Disclosure of authentication information, Disclosure of user information, Execution of arbitrary code via network, Modification of user information
|
Exploit Included: Yes
|
Version(s): 7.1.0
|
Description: Several input validation vulnerabilities were reported in PHP-Nuke. A remote user can conduct cross-site scripting attacks.
Janek Vind (waraxe) reported that several modules do not properly filter scripting code from user-supplied input. A remote user
can create a specially crafted URL or POST request that, when loaded by a target user, will cause arbitrary scripting code to be
executed by the target user's browser. The code will originate from the site running the PHP-Nuke software and will run in the security
context of that site. As a result, the code will be able to access the target user's cookies (including authentication cookies),
if any, associated with the site, access data recently submitted by the target user via web form to the site, or take actions on
the site acting as the target user.
The following fields and modules are reportedly affected:
1) The 'Email' and 'Your Name'
fields of the Feedback module.
2) The 'nicname' field of the Your_Account module (with 'pass_lost' as the 'op' variable).
3)
The 'fname' variable of the Recommend_US module (with 'SiteSent' as the 'op' variable).
4) The 'ratenum' field in the Downloads
module (with 'TopRated' for the 'op' variable).
5) The 'search' field of the Journal module.
It is also reported that cookie
parameters for all affected variables can also be used in conducting cross-site scripting attacks.
|
Impact: A remote user can access the target user's cookies (including authentication cookies), if any, associated with the site running the
PHP-Nuke software, access data recently submitted by the target user via web form to the site, or take actions on the site acting
as the target user.
|
Solution: No solution was available at the time of this entry.
|
Vendor URL: www.phpnuke.org/ (Links to External Site)
|
Cause: Input validation error
|
Underlying OS: Linux (Any), UNIX (Any), Windows (Any)
|
Reported By: Janek Vind <come2waraxe@yahoo.com>
|
Message History:
None.
|
Source Message Contents
|
Date: 15 Mar 2004 18:39:48 -0000
From: Janek Vind <come2waraxe@yahoo.com>
Subject: [waraxe-2004-SA#005 - XSS in Php-Nuke 7.1.0 - part 2]
|
{================================================================================}
{ [waraxe-2004-SA#005] }
{================================================================================}
{ }
{ [ XSS in Php-Nuke 7.1.0 - part 2 ] }
{ }
{================================================================================}
Author: Janek Vind "waraxe"
Date: 15. March 2004
Location: Estonia, Tartu
Affected software description:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Php-Nuke is popular freeware content management system, written in php by
Francisco Burzi. This CMS (COntent Management System) is used on many thousands
websites, because it`s free of charge, easy to install and has broad set of features.
Homepage: http://phpnuke.org
Vulnerabilities:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Through the history of the PhpNuke there has been lots of messages and announcments
about the Cross-Site Scripting aka XSS problems in this popular content management system.
Now PhpNuke has allready version number 7.1.0, but still we can't say, that it's secure
software. This advisory - "waraxe-2004-SA#005" - is meant to uncover some more XSS cases,
besides those published earlier by me in "waraxe-2004-SA#002".
So, let's begin...
1. http://localhost/nuke71/modules.php?name=Feedback
If we use in "Your Name" field the string:
"><body onload=alert(document.cookie);>
then we have XSS conditions. Same applies to email field.
2. http://localhost/nuke71/modules.php?name=Your_Account&op=pass_lost
In "nicname" field we use "><body onload=alert(document.cookie);> and XSS
is available.
Remark - you need to make custom form, because in the original html code there is
limited length of the "nicname" text field - 15 symbols.
3. http://localhost/nuke71/modules.php?name=Recommend_Us&op=SiteSent&fname=>[xss code here
]
Remark - because the GET parameters are filtered in PhpNuke, we need to bukd custom html code
with proper form and then use POST parameters to complete the mission. By the way - even COOKIE
parameters can be used for this and it`s really handy, because COOKIE stuff get's rarely logged by
web server software. This applies to all XSS cases in PhpNuke, because the use of the code
"import_request_variables('GPC');" in the mainfile.php ;)
4. http://localhost/nuke71/modules.php?name=Downloads&d_op=TopRated&ratenum=>[xss code her
e]&ratetype=x
5. http://localhost/nuke71/modules.php?name=Journal&file=search&disp=showsearch
We can exploit the search field for implement the XSS.
Finally - if we use XSS, we can steal cookies, use them to pretend to be somebody else (authenticatio
n
bypass), and if the victim of the impersonating has admin rights in PhpNUke, then the entire website
is allready compromised...
Greetings:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Greets to ulljobu, djzone, raider and to all IT freaks in Estonia!
Contact:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
come2waraxe@yahoo.com
Janek Vind "waraxe"
---------------------------------- [ EOF ] ------------------------------------
|
|
Go to the Top of This SecurityTracker Archive Page
|
