full-disclosure - XSS vulnerability in XOOPS 2.0.5.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <BAY8-DAV57bme3S97K50000fdf1@hotmail.com>
From: chesschintan at hotmail.com (Chintan Trivedi)
Subject: XSS vulnerability in XOOPS 2.0.5.1

====================================================================
Advisory by Eye On Security Research Group - India www.eos-india.net 
====================================================================




1...............................................................Product
2................................................................Vendor
3.........................................................Vulnerability
4.........................................................About Product
5..............................................Details of vulnerability
6...............................................................Exploit
7...............................................................Credits




1. Product 
==========

XOOPS 2.0.5.1


2. Vendor
=========

www.xoops.org


3. Vulnerability
================

XSS vulnerability in module weblinks


4. About XOOPS
==============

XOOPS is a dynamic OO (Object Oriented) based open source portal script written in PHP. XOOPS supports a number of databases, making XOOPS an ideal tool for developing small to large dynamic community websites, intra company portals, corporate portals, weblogs and much more. 


5. Details of vulnerability
===========================

The weblinks module contains a file named "myheader.php" in /modules/mylinks/ directory. The code of the file is as follow : 

---------------------------------
include "../../mainfile.php";
$url = $HTTP_GET_VARS['url'];
$lid = intval($HTTP_GET_VARS['lid']);



<td class='bg4' align="center"><small>
<a target="main" href="ratelink.php?cid=<? echo $cid; ?>&amp;lid=<? echo $lid; ?>"><? echo _MD_RATETHISSITE; ?></a> | <a target="main" href="modlink.php?lid=<? echo $lid; ?>"><? echo _MD_MODIFY; ?></a> | <a target="main" href="brokenlink.php?lid=<? echo $lid; ?>"><? echo _MD_REPORTBROKEN; ?></a> | <a target='_top' href='mailto:?subject=<? echo $mail_subject; ?>&body=<? echo $mail_body;?>'><? echo _MD_TELLAFRIEND; ?></a> | <a target='_top' href="<? echo XOOPS_URL; ?>">Back to <? echo $xoopsConfig['sitename']; ?></a> | <a target='_top' href="<? echo $url; ?>">Close Frame</a>
</small>


-----------------------------------

The value for variable "url" is used in line 
<a target='_top' href="<? echo $url; ?>">Close Frame</a>

Thus an attacker can pass a javascript code as a value for variable url and get it executed as soon as the victim clicks the "Close Frame" link.


6. Exploit
==========

http://[target]/modules/mylinks/myheader.php?url=javascript:alert(document.cookie);

Clicking the above link, the victim gets directed to a page containing a link "Close Frame" which is actually the javascript code inserted by the attacker. The cookie revealed is quite informatic for the attacker to login with the hijacked user (including admin) privileges. 


7. Credits
==========

Chintan Trivedi - http://www.hackersprogrammers.com
"Eye on Security Research Group - India " - www.eos-india.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20031121/d7aac58b/attachment.html