PEAK XOOPS - Installer Attack 
XOOPS
XOOPS : Installer Attack
Do you know 'intaller attack'?
If you leave 'install' folder in the public area of the server, attacker can know your DB password, DB prefix etc.
You should know attackers know the folder of 'install' can be renamed '_install' etc.
This is certainly a mistake of the user.
But I find checking a constant '_INSTALL_CHARSET' can protects your xoops from such attacks.
I've just updated the module Protector numbered 3.03 with the feature.
If you dare to use the installer after installing Protector, remove the precheck line from your mainfile.php
Comments list
GIJOE
Posted on 2007/6/3 17:01 | Last modified
hi tl.
Quote:
I know several XOOPS sites with '_install' directory.
Attackers can know the sites informations easily via accessing XOOPS_URL/_install/index.php
Of course, there are too many patterns of renaming by users.
(install_, install.bak etc.)
admin.php cannot search all patterns.
Just adding a line checking whether '_INSTALL_CHARSET' is defined or not makes all patterns safe.
(The line is enough light to be ignored)
Thus, I've judged this is worthy code for Protector.
Quote:
tl wrotes:
Well, if people have been reminded constantly by Xoops Admin and don't even bother to remove the install directory, they may deserve to be attacked and not worthy of Protector protection?
I know several XOOPS sites with '_install' directory.
Attackers can know the sites informations easily via accessing XOOPS_URL/_install/index.php
Of course, there are too many patterns of renaming by users.
(install_, install.bak etc.)
admin.php cannot search all patterns.
Just adding a line checking whether '_INSTALL_CHARSET' is defined or not makes all patterns safe.
(The line is enough light to be ignored)
Thus, I've judged this is worthy code for Protector.
tl
Posted on 2007/6/3 8:22
Well, if people have been reminded constantly by Xoops Admin and don't even bother to remove the install directory, they may deserve to be attacked and not worthy of Protector protection? 
Login