vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   General Articles (https://vborg.vbsupport.ru/forumdisplay.php?f=189)
-   -   Preventative - How to avoid being Hacked by TeamPS i.e. p0wersurge (https://vborg.vbsupport.ru/showthread.php?t=275719)

TheLastSuperman 12-19-2011 11:00 PM

Preventative - How to avoid being Hacked by TeamPS i.e. p0wersurge
 
No doubt some of you have already been defaced at some point in the past, what I aim to do is make a quick post letting you know a few simple tips to avoid or recover from this and also help you re-secure your site if you've recently recovered from such activity.

Lately what I've noticed is on older versions namely pre 4.1.4 a group of hackers have been exploiting the Admin Username and Password through member groups and the search feature, granting them access to the forum in question to do so as they wish. The main goal of the information outlined below is to help you prevent this from happening by adding in some additional security to your admin and moderator control panels with .htaccess. Initially newer versions were not affected by this however after a recent post on vBulletin.org I'm not sure what other methods they are using - https://vborg.vbsupport.ru/showthread.php?t=275715 so let's go ahead and remedy this shall we?

____________________

If your currently secure:
1) .htaccess protect your admincp and modcp here are some useful links;
.htaccess authentication generator:
http://www.htaccesstools.com/htaccess-authentication/
.htaccess password generator:
http://www.htaccesstools.com/htpasswd-generator/

Now if they are able to somehow obtain your primary admin account username and password they can only do so much damage... why? Well your admin control panel now requires a completely different username and password before you can even login, without server/ftp access they can never bypass this.

____________________

If you've been defaced:
1) Try restoring to a backup before you were hacked, if not possible recover the best way you can.
2) Change database passwords *Don't forget to update the config.php files for vBulletin and any other software running on your site.
3) Change FTP account passwords.
4) Change admin account passwords.
5) .htaccess protect your admincp and modcp here are some useful links;
.htaccess authentication generator:
http://www.htaccesstools.com/htaccess-authentication/
.htaccess password generator:
http://www.htaccesstools.com/htpasswd-generator/
6) Check to see if they added any admin accounts, on one site they changed the primary admin account name to what they desired and went so far as to re-create the admin accounts w/ the same details but no admin permissions to throw the site owners off for a little bit.
7) Use this guide and ensure your site is 100% clean - http://www.vbulletin.com/forum/blogs...iller/3934768-

___________________

*Use a entirely different username and complex password when creating the .htaccess and .htpasswd files. Also on that note, be sure the .htpasswd is stored above public_html i.e. in /home/accountnamehere/.htpasswds

**Wayne Luke of the vBulletin.com team also posted some very sound advice here, please take the time to read his post - https://www.vbulletin.com/forum/show...=1#post2245651

ReFuZe 12-22-2011 04:41 PM

lolz that doesnt secure you at all it only secures the admincp but not that good theres tools for it I know becuase ive seen people do it and i had it all you need is a good hosting with alot of security cloudflare htaccess and no vuln and all that thats how you get secured

TheLastSuperman 12-22-2011 06:58 PM

Quote:

Originally Posted by ReFuZe (Post 2280113)
lolz that doesnt secure you at all it only secures the admincp but not that good theres tools for it I know becuase ive seen people do it and i had it all you need is a good hosting with alot of security cloudflare htaccess and no vuln and all that thats how you get secured

I've never understood posts like the one above ^ - Not trying to be rude but either post "How-To" or don't post comments like that at all in my threads please, anywhere else go ahead however imo it does help if the one gaining access to your site knows nothing more than the context of the tutorial or video he/she is viewing correct? Case in point.

Your exactly right though, there's other ways that are much better however in my initial post above I clearly stated:

Quote:

what I aim to do is make a quick post letting you know a few simple tips
Pay attention and read between the lines so your not presented with a response like this in the future, everyone should be well prepared :cool:.

socialteenz 12-24-2011 09:25 AM

Great article. You are definitely a superman.

CharlieDelta 12-24-2011 05:50 PM

Quote:

Originally Posted by socialteenz (Post 2280656)
Great article. You are definitely a superman.

No he is not....he is the LAST SUPERMAN!! ;)

Thank you for this article. :up:

ReFuZe 12-26-2011 01:25 PM

Check my Article out that secures your site from Shells. plus Im working a tool that scans and when finds shells it removes them me and relevant are doing it so once its done it will be out to public but in the mean time use my article look at my threads

--------------- Added [DATE]1324909616[/DATE] at [TIME]1324909616[/TIME] ---------------

Im a pro hacker and a pro secure I know alot of basic but vb4.1.9 had too many LFI and RFI docks in them so thats why they are easir plus thats why I made my thread on how to block shells ill make a tut later


Sorry for my grammer just woke up

JimxJNM 01-01-2012 12:10 AM

Quote:

Originally Posted by ReFuZe (Post 2281108)
Check my Article out that secures your site from Shells. plus Im working a tool that scans and when finds shells it removes them me and relevant are doing it so once its done it will be out to public but in the mean time use my article look at my threads

--------------- Added [DATE]1324909616[/DATE] at [TIME]1324909616[/TIME] ---------------

Im a pro hacker and a pro secure I know alot of basic but vb4.1.9 had too many LFI and RFI docks in them so thats why they are easir plus thats why I made my thread on how to block shells ill make a tut later


Sorry for my grammer just woke up


Basically vBulletin websites doesn't have RFI / LFI Injections... In based the files aren't supporting these kind of LFI or RFI injections... Just letting you know ;)

ReFuZe 01-08-2012 06:49 PM

Yeah I know, I thought they where. Tm currently working on my tool to prevent hacking and shells. It might be possible but my other coder said it will take time.

Eslob 01-29-2012 10:42 AM

the best method is to encypt the config.php & class_core.php.

and keep a backup on ur pc.

and disable html in posts.

and change the path for config.php & change admincp folder to other and keeping the old name as an ambush.

Angel-Wings 05-06-2012 01:44 PM

Quote:

Originally Posted by Eslob (Post 2293782)
the best method is to encypt the config.php & class_core.php.

Sorry but someone who could access your server to have read rights for config.php (meaning the code) would have no problems with a simple copy & paste and then decode everything.

One thing to add maybe - if the site got defaced then the usual way would be to do a complete reinstall. Just copying in backups would also copy the security issue again someone used for the defacement.


All times are GMT. The time now is 11:42 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01377 seconds
  • Memory Usage 1,749KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (5)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (2)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete