The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#11
|
|||
|
|||
![]()
mine is a dedicated server and no I had no security setup. I learned the hardway.... but now I know and I am locked up tighter than hillary clintons underoos.......
|
#12
|
|||
|
|||
![]()
Another possiblity: You used this password on another forum/service, thus got hacked, so they got your password. Don't laugh, this is happening!
Quote:
bw, Stefan |
#13
|
||||
|
||||
![]() Quote:
Quote:
Other tools like fail2ban that scan logs for possible bruteforce attacks and block IP's can do a lot of damage - Logfile injection as example so you've a nice SelfDoS. Also, in a world of bot nets where private comps are abused blocking IP's usually hits the wrong people - the real attacker simply uses the next comp, another IP and continues. Generally - check all files on your server and compare them with the original ones from trusted sources. Both the PHP files and the OS files. Then changing Passwords may be useful - all this just in case some hidden backdoor has been installed |
#14
|
|||
|
|||
![]()
Yah, I had the same problem with someone attacking my forum with the sniper_sa. Here is the post I had made with the same. I'm am assuming they were using the script to grab either my admin login/pw or database login/pw. I also have a list of files that I found.
https://vborg.vbsupport.ru/showthread.php?t=192151 |
#15
|
||||
|
||||
![]()
Unless they can crack your password (which would take years), they don't know it. If they could upload files directly though, though could just create a new user as admin, or log themselves in as you if they knew how vBulletin worked well enough.
|
#16
|
||||
|
||||
![]() Quote:
do they really get your password? or just they got a way to enter? because I just saw the extra files, a cronjob, a new email account, and a few ftp transfers, and I got thousands worth of domains and scripts.... ![]() |
#17
|
|||
|
|||
![]()
I uploaded the sni.php to another server that I own and played around with it. It allows you to upload, download and edit files on on the server. so if they can find config.php they can download it and view it's contents (ie db login/pw) and then use the sni.php to enter the login/pw to access the db. It also allows you to use sendmail, FTP (if login/pw known) and some other stuff.. it can be very damaging in the wrong hands.
|
#18
|
||||
|
||||
![]()
Now tell me the good news!
![]() how we can avoid that? how many files of this kind there's? |
#19
|
||||
|
||||
![]() Quote:
How can you avoid it? Don't let anyone be able to upload files files directly. (Attachments are OK, they are correctly stored by vBulletin.) How many of these files are there? There are probably thousands of shells available to freely download. |
#20
|
|||
|
|||
![]()
I did some more searching over the last couple days and there were some issues, exploits, vulnerabilities or whatever, where files (other than images) can be uploaded using vbpicgallery, photpost classifieds, and photopost vbgallery, and vbadvanced cmps. All of them seem to have been resolved except for vbadvanced cmps, or at least not that I could find. It's kind of my fault that I haven't been keeping up with the updates, but I haven't been receiving any notifications that any new updates have been released.
What I've been doing over the last few days is using woopra to track all of the visitors whose languages are arabic, and banning those IP's. So far, using those IP's and searching the logs, they've been attempting to access the directories where the old sniper_sa scripts were and have also helped me locate where other scripts have been placed within my site. After a few days of watching, I've done an IP ban on the internet provider that this guy has been using, which is also a very common ip used by hackers and spammers.. 213.0.0.0/8. This pretty much blocks all IP's from 213.0.0.0 to 213.255.255.255. if you do a reverse IP lookup on the spammer/hacker you can sometimes view the ISP's info and it will tell you the IP's that they cover, in this case, start IP was 213.0.0.0 to 213.255.255.255. If you're not familiar with how to block IP's, here is how you do it. If you search for .htaccess and deny IP you can find some documentation on it. <Files 403.shtml> order allow,deny allow from all </Files> deny from 212.14.224.2 deny from 84.41.118.98 deny from 213.0.0.0/8 deny from 193.0.19.25 |
![]() |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|