 |
|
 |
 |
Menu |
 |
|
 Home |
| |
|
 Discussions |
| |
|
 Tools |
| |
|
| Affiliates |
| |
|
 Content |
| |
|
 Info |
| | |
|
|
|
|
|
User Info |
|
 Membership:
 Latest: MichaelSnaRe
 New Today: 0
 New Yesterday: 0
 Overall: 9144
 People Online:
 Visitors: 105
 Members: 0
 Total: 105
|
|
|
|
|
|
Full disclosure |
|
|
|
 |
|
 |
 |
|
 |
IT Security and Insecurity Portal |
|
|
vBulletin 3.8.6 - Critical Information Disclosure |
|
 Posted: Sat Jul 24, 2010 4:42 pm |
 |
|
| VERTIGO |
| Advanced user |
 |
|
| Joined: Sep 25, 2008 |
| Posts: 87 |
|
|
|
 |
|
 |
|
| Code: | vBulletin - Critical Information Disclosure
Versions Affected: 3.8.6 (Only!)
Info:
Content publishing, search, security, and more—vBulletin has it all. Whether
it’s available features, support, or ease-of-use, vBulletin offers the most for
your money. Learn more about what makes vBulletin the choice for people
who are serious about creating thriving online communities.
External Links:
http://www.vbulletin.com/
Credits: Floris from vbfans.com
-:: The Advisory ::-
vBulletin is prone to information disclosure of the entire database
credentials used in config.php via the faq.php file.
By searching for "database" on a vulnerable installation of vBulletin
an attacker is shown the information mentioned above.
-:: Solution ::-
A patch is available from http://members.vbulletin.com
Alternatively, search for "database_ingo" in the Phrase Manager
within the Admin Control Panel, and delete or edit all critical details.
Disclosure Information:
- vBulletin Security Notice & Patch: 22nd July 2010
- Vulnerability Researched and Disclosed: 22nd July |
|
|
|
|
|
|
|
|
|
| Posted: Sun Jul 25, 2010 4:08 pm |
|
|
| waraxe |
| Site admin |
 |
|
| Joined: May 11, 2004 |
| Posts: 2407 |
| Location: Estonia, Tartu |
|
|
|
|
|
|
I did some quick real world scanning and there are very few exploitable targets right now. Mitigating factors:
1. Only 3.8.6 version is vulnerable
2. most installations are already patched
3. even if you have mysql credentials, they can be already changed
4. mysql daemon must be remotely accessible - tcp port 3306 needs to be open
5. "Host 111.222.223.113 is not allowed ..." -> this is what you can get frequently, because specific mysql user is configured to be able to log in from specific IP address(es) only, usually 127.0.0.1 |
|
|
|
|
www.waraxe.us Forum Index -> vBulletin Board
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
All times are GMT
Page 1 of 1
|
|
|
|
Powered by phpBB © 2001-2008 phpBB Group
|
|
|
|
|
|
|
