Greetings,
GMTonyKosten wrote on 10/29/07 at 22:05:56:
Markovich wrote on 10/29/07 at 18:27:50:
Yes, I'd be very interested to know if this was a Unix/Linux/BSD machine or a Windows one. In fairness though, I think there are external things you can do to bring a not-too-well-defended Unix server down.
The real issue is security on the server. I wonder what vulnerability was exploited, and why the system was vulnerable in the first place.
It is a Unix with Apache, and the IT guys suspected some vulnerability in the Forum software. I went to the YaBB Forum to ask if this was possible and they denied there were any holes, or at least no more than you would expect from free software!
Anyway, this is why the Forum has moved to another site. If it gets hacked again it won't bring down the main site!
Bearing in mind the above and the earlier posts by
Alien chess and others...
On a UNIX system, hackers gain access to the "root" (equivalent to the Windows "admin" level user) - hence the term, "rootkit" - through compromised passwords or by exploiting a known vulnerability in a service running on the system. Once they have root access, they can do pretty much anything they want - they can come and go as they choose by use of a installed "backdoor"; the rootkit is installed as a means of hiding such activity.
Once the system has been compromised, removing a rootkit from UNIX is nigh impossible - a format/reinstall is necessary.
One must, therefore, have a good security policy in place to prevent, in the first instance, and recover from such compromising of the system.
The UNIX system must be locked-down as much as possible - only run the needed services/scripts, the fewer such running on a system, the less opportunity is afforded the hacker. Lock down user accounts - no shell access unless required.
Compile services from source (including Apache) oneself.
It is critical to have a update notification service - for any/all available updates - and ensure that these are installed.
Run
rootkit scanners daily - Tripwire ("payware") or AIDE (free equivalent of Tripwire - NOT a free version of Tripwire!), chrootkit and/or RKHunter - and send the output to people who'll act upon the reports.
Install and run network monitoring software on the whole network - nmap and/or SNORT. Again, send the output to those who'll act upon it. [They'll show up backdoors for a start.]
Ensure that you have a hardware firewall as well as IPTables (for filtering packets based on rules).
Take separate daily backups of the operating system, applications and data. That way, you'll only "lose" one day's data, at worst.
The above is just a quick rules-of-thumb guide for your "IT guy" - it isn't definitive!
Speaking of updates...
I note you're currently running 2.1 - I don't know what version you were running beforehand, most likely this version from what I've seen on the site.
However, they've just released (8 Nov) a newer version -
YaBB 2.2 - which includes several security and anti-spam enhancements.
NOTE: If your site includes lots of 2.1 "mods", these won't work under 2.2 (from what I've read there). They also recommend backing up the whole forum - several times for safety reasons - before installing the new version in it's own separate directory.
See also
http://www.yabbforum.com/community/?board=general;action=display;num=1194579334.
Kindest regards,
Dragan Glas