vBulletin 'misc.php' Lets Remote Users Injection PHP Code via the 'template' Parameter
SecurityTracker Alert ID: 1013261|
SecurityTracker URL: http://securitytracker.com/id/1013261
(Links to External Site)
Date: Feb 22 2005
Execution of arbitrary code via network, User access via network|
Fix Available: Yes Vendor Confirmed: Yes Exploit Included: Yes |
Version(s): 3.0.6 and prior versions|
A vulnerability was reported in vBulletin in the processing of template names. A remote user can execute PHP commands in certain cases.|
If the 'Add Template Name in HTML Comments' option is enabled (which is not the default configuration and is not recommended by the vendor for use in a production environment), a remote user can submit PHP code in the 'template' parameter in 'misc.php'.
A demonstration exploit URL is provided:
The vendor was notified on February 18, 2005.
pokley from SCAN Associates reported this vulnerability.
A remote user can execute PHP commands on the target system with the privileges of the web service.|
The vendor has issued a fixed version.|
The report indicates that, as a workaround, you can disable the "Add Template Name in HTML Comments" option.
Vendor URL: www.vbulletin.com/ (Links to External Site)
Input validation error|
|Underlying OS: Linux (Any), UNIX (Any), Windows (Any)|
Source Message Contents
Subject: [Full-Disclosure] : [SCAN Associates Security Advisory] vbulletin|
Summary: vbulletin 3.0.6 and below php code injection
vBulletin is a powerful, scalable and fully customizable forums package
for your web site. It has been written using the Web's quickest-growing
scripting language; PHP, and is complimented with a highly efficient and
ultra fast back-end database engine built using MySQL.
User may inject php code using "nested variable" into template name when
"Add Template Name in HTML Comments" is enable. This option is not enable
by default and is not recomended by vbulletin for production environment.
The problem occur when user may supply partial template name through
Disable "Add Template Name in HTML Comments" option.
Proof of concept
17th February 2005 - Vulnerability found
18th February 2005 - vbulletin developer informed
19th February 2005 - vbulletin developer confirmed
20th February 2005 - Fix Available from vbulletin team
Full-Disclosure - We believe in it.