QUOTE (Jeff @ Jun 19 2008, 03:40 AM)

Questions:
1.) was the "solid proof" you submitted really proof that couldn't be forged by anyone with a text editor such as pico or notepad?
I'm not defending a slow abuse response, but it seems all cases will need to be investigated because there's zero room for error when interrupting all the legitimate customers on the server. I would think you supplied solid evidence, but not solid proof since a snip of logs could be forged by a malicious person.
The Planet staff have the ability to log in to my server (since it is a dedicated in their data center) and view the logs and mod_security results themselves, or even just log into my WHM > Plugins > Mod Security and see the attack right there (if there was any doubt as to the validity of the ticket I submitted), so I'm not sure how much more solid you can get. A malicious person trying to forge an abuse report wouldn't submit a ticket and then simultaneously call TP support and offer/ask them to log in to their own server to see for themselves what was happening, which is exactly what I did as soon as I saw it happening. Though I try to avoid calling support whenever possible, it's always best to call them and ask them to look at the server so that they can see for themselves exactly what is happening while it's happening.
QUOTE (Jeff @ Jun 19 2008, 03:40 AM)

2.) how serious was the attack (something that will be caught by default mod security rules, or something more advanced) and is it currently ongoing against your firewall or was it a one time attack that subsided (I believe your post above says yes the attack is still going hitting your firewall every x-seconds/minutes, but I just want to be 100% clear on this)?
I'm not quite sure how you personally define the seriousness of an attack, but this was an SQL Injection attack against the PHP script / database of sites that are powered by PHP scripts and use galleries. This is a typical / common method that porn spammers use to execute their own scripts through the victim's PHP/database-driven site for purposes of everything from utilizing the victims site to send out spam all the way to using the search results of a legitimate victim site to raise search engine rankings and create spoof links to the offenders porn site. My mod_security alert logs show that the attack was hitting every 1.5 seconds until my security system blocked them off. As far as "ongoing", it likely would have been but I then permanently blocked the IP via my LFD iptables firewall software, since the mod_security blocks are only temporary (so as not to permanently block a false-positive from a legitimate user or script), so it didn't "subside", I subsided it myself, so-to-speak.
Just to give you an idea of the type of attack, here is a small excerpt from the mod_security log (all IP's and site/hostnames and other identifiers replaced with X's so as not to upset anyone):
IP of attacker: xx.xx.xx.x (x.xx.xxxx.static.theplanet.com)
[client xx.xx.xx.x] ModSecurity: Access denied with code 406 (phase 2). Pattern match "(?:\\\\b(?

?:s(?:elect\\\\b(?:.{1,100}?\\\\b(?

?:length|count|top)\\\\b.{1,100}?\\\\bfrom|from\\\\b.{1,100}?\\\\bwhere)|.*?\\\\b(?

(?:ump\\\\b.*\\\\bfrom|ata_type)|(?:to_(?:numbe|cha)|inst)r))
|p_(?

?:
addextendedpro|sqlexe)c|(?:oacreat|prepar)e|
execute(?:sql)?|makewebt ..." at ARGS:gallery_id. [id "950001"] [msg "
SQL Injection Attack. Matched signature <union select>"] [
severity "CRITICAL"]
[hostname "xxxxxxxxxxxxx.com"] [uri "/gallery2.php?gallery_id=30%20union%20select%20null%2Cnull%2C%27just_a_test_3_%20%3C%3Fphp%20echo%28md5%28%22just_a_test%22%29%
29%3B%20echo%28%40unlink%28%22%2Fhome%2Fxxxxxx%2Fpublic_html%2Fjatest.php%22%29%20%3F%20%22un%22.%22linked%22%20%3A%20%22not_un%22.
%22linked%22%29%20%3F%3E%27%20into%20outfile%20%27%2Fhome%2Fxxxxxxxx%2Fpublic_html%2Fjatest.php%27"] [unique_id "WtS@xxxxxxxxxxxxxx-xxxxxxx"]
As you can see, the offending server in that instance is running a script that is attempting to execute an SQL command in the gallery portion of the PHP script on the victim's site, attempt to plant a file in the public_html folder of the victim, and testing to see if they could get the uploader portion of the script to accept/execute their own script, for various purposes which you can imagine - everything from using the script to send out spam, to spoofing search links, to defacing / disabling the victims pages.
To me, any such attack is "serious" and any site/server executing it should be immediately suspended, which can be done without taking down an entire server or affecting other customers on it. As a host yourself, you probably know that all you have to do is log in to your server and suspend that particular site's account and log in / remove the scripting files from their account.