fozl
20-08-2010, 15:05

As for the log, you still seem to fail to grasp that the log is impossible unless they somehow manage to break .htaccess.
What my answer mean is:
- your server has been suspended because WE intervent always when our network security is in danger.
In your case for example this mean: if we let the incoming attack still the same, switch performances going down, if your server can not resist and the attack is successful your server start to be an zombie and can be an danger for others )
And so we send an generic message to the server admin.
***************SNIP*****************
- is your server hacked? we do not know, because you know your server and I'm sure you have now checked everything
All what we can do is provide this informations and explain you that whenever something will be an danger for our network: we will intervene
xxx:/home# zgrep '207.182.151.24' /var/log/*/*
/var/log/lighttpd/access.log.1.gz:94.1xx.xx.xx xxx.xxomseedbox.com xxx[11/Aug/2010:15:38:51 +0200] "GET /udp.php?act=phptools&host=207.182.151.24+&time=2 HTTP/1.1" 200 874 "http://xxxx.xxomseedbox.com/udp.php" "Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 (.NET CLR 3.5.30729)"
Apparently that is the proof my server is hacked. Well, firstly, udp.php doesn't exist in that users www directory. It also doesn't exist in the servers www directory (which is blank btw).
... (blah blah) ...
$rand = rand(1,65000);
$fp = fsockopen('udp://'.$host, $rand, $errno, $errstr, 5);
2010-08-11 17:03:50 2010-08-11 17:03:50 94.??.??.14 vi??.??omseedbox.com 43429 207.182.151.24 2413 UDP 1 1500 2010-08-11 17:03:49 2010-08-11 17:03:49 94.??.??.14 vi??.??omseedbox.com 45603 207.182.151.24 59724 UDP 1 1500
> server 8.8.8.8 Default Server: google-public-dns-a.google.com Address: 8.8.8.8 > 207.182.151.24 Server: google-public-dns-a.google.com Address: 8.8.8.8 Name: 18.97.b6.static.xlhost.com Address: 207.182.151.24 >
ITS NOT A EFFING WINDOWS BOX, OVH ARE JUST RETARDS.
You can check section 5.2 of the contract that relates to liabilities etc in the case of loss of service or data due to attacks. To challenge this decision you need to provide information that we could examine that proves the hack status was not a false positive.
Regards, Folarin.
From : Celine S.
For: jd6756-ovh
Date: 2010-08-16 14:44:46
Dear customer,
The incoming attacks are due to the content or
the server's activity,
and to the competition in this sector often
illegal or subject to controversy.
The use of the torrent is not allowed on servers
of ovh.
Kind regards,
Celine S
# attack requirements:
# 1) vulnerable version (obviously!): 2.11.x before 2.11.9.5
# and 3.x before 3.1.3.1 according to PMASA-2009-3
# 2) it *seems* this vuln can only be exploited against environments
# where the administrator has chosen to install phpMyAdmin following
# the *wizard* method, rather than manual method: http://snipurl.com/jhjxx
# 3) administrator must have NOT deleted the '/config/' directory
# within the '/phpMyAdmin/' directory. this is because this directory is
# where '/scripts/setup.php' tries to create 'config.inc.php' which is
where
echo deb http://ftp.fr.debian.org/debian sid main >> /etc/apt/sources.list
Package: * Pin: release a=stable Pin-Priority: 700 Package: * Pin: release a=unstable Pin-Priority: 600
aptitude update
apt-get install phpmyadmin/unstable
apt-get -t unstable install phpmyadmin
Dear customer, Hack details: http://travaux.ovh.net/?do=details&id=4452 The offending script is not one of your scripts but phpMyAdmin fault. You must update this phpMyAdmin. The used fault: http://securityreason.com/exploitalert/6399 Check the logs of your machine: cd / var / log / votredossierdeslogsapache egrep-ri 'POST' * | grep phpmyadmin | grep setup We turn the machine in rescue mode . Thank you to update your phpMyAdmin before restarting the server in boot. If you would like us to carry the update we can offer this for 20 Euro HT. Kind regards, Mrayam J