Forum Moderators: rogerd
The latest version (2.0.11) is now available from phpbb.com which corrects the problem, so you need to update your installation as soon as possible.
If you can't update straight away, at least apply the fix as described here:
[phpbb.com...]
If you don't update and you subsequently have problems, don't say we didn't warn you ;)
I renamed my forum directory to forumOLD, as a temp backup just in case I ran into a problem.
I downloaded 2.0.11, and uploaded it to the original forum directory, but did not upload the install and contrib files.
Then I uploaded my original config file from forumOLD.
Everything seems to work fine.
Is this OK, or is there a reason to run install again?
Doing it this way only took 5 minutes, and is an easy fix for anyone if it works OK.
Thanks!
I am not asking for anything like that. Telling people to invent their scripting language, then writing a script for it would.
All I am saying is, instead of asking me for the time, buy a watch, and put it on your wrist. You do not believe me, but I've seen it. People have more trouble configuring 3rd party software than they would if they maintained their own scripts. Believe me, it's worth the time. Learn PHP and MySQL, you will feel like you own your site. Also, hackers have better things to do than write cracks for scripts that only a few people use.
One fairly scary aspect about this exploit is that many web hosts will auto-install phpBB for their shared hosting clients; it's free, and well-regarded. Now, these hosts have hundreds or thousands of installations that may be compromised. Usually, the software is maintained by the user after initial installation - they may have applied hacks or changed code on their own, which means the host can't just slap in replacement code. Messy situation...
Dillonstars: the upgrade from 2.0.10 to 2.0.11 won't directly affect any templates, so you should be okay. If you have any mods installed, you might have to reinstall them if they've modified files that are included in the 2.0.11 upgrade.
Faltered: you won't lose any of your current threads or settings by upgrading to 2.0.11 -- but, as with any upgrade, be sure to back up your database and forums directory first. And based on what's going on with the forums that *haven't* been modified, there's definitely a chance you could lose everything if you don't upgrade...
Good luck!
Dave
[Edit: if you use the Changed Files Only method, you need to set up an install folder under your phpBB2 folder, put the update_to_2011.php file in it, then open a browser window and navigate to your phpBB2 folder and run the update file to change the version number....]
[edited by: vkaryl at 2:46 am (utc) on Dec. 14, 2004]
I have added a thread with some ideas for improving general security here [webmasterworld.com].
Does anyone know if the 'Hackers'can access other files on your website besides the PHPBB forum files through this PHPBB exploit? One of my sites that was running a PHPBB forum and also other pages, was first defaced and then deleted recently. Just wondering whether the hackers used this exploit. I had a backup so was able to restore the site without much problem. But since then I have deleted the PHPBB forum from that site.
Under most common hosting setups, if an attacker breaks in using the 2.0.11 exploit they can access ANY file on the Whole Server!
This is due to the expoit providing shell access as the web server user, and unless you are running php under cgi mode ( rare ) then all websites run as the same user.
So even if you have patched phpBB, if someone else on your server is running an unpatched version you could still be at risk.
And once your site or someone elses site is hacked, they can install a back door and even phpbb will not help. This is common btw, happened on 2 of my servers using 3 different back doors. PHPBB did not disclose this properly and I had a go at them, resulting in the 2.0.11 upgrade reminder annoucement thread.
My suspecioin was that this caused the crash and I upgraded immediatly. Worst part is that I knew of the security upgarde but didn't think it was so serious and ignored it :(