Forum Moderators: phranque

Message Too Old, No Replies

Security problem on my server

         

Raymond

10:42 am on Feb 3, 2007 (gmt 0)

10+ Year Member



I have received an email from my host telling me that my server has been trying to scan another IP's port 1521. The log they sent me contains my main server IP using ports (3181 - 3235), (probably more ports but they only sent this part), scanning the destination IP port 1521.

I am the only user on the server. I tried to look at the event log and I didn't find anything particularly suspicious. There are a few FTP failed attempts though.

Is there anywhere I should look? What could have caused this? Is this an hack attempt on my server, and theirs?

Any help is greatly appreciated. Thank you.

jatar_k

2:27 pm on Feb 6, 2007 (gmt 0)

WebmasterWorld Administrator 10+ Year Member



is your server managed? or are you the admin for your own server?

port 1521 seems to be common for oracle listener services, though in the port list [iana.org] it is 'nCube License Manager'

those two things might be something to look at

Raymond

4:37 am on Feb 8, 2007 (gmt 0)

10+ Year Member



I found a trogan called Exploit-DFind on my server. I have no idea how it got in. Also, the guest account on my server was set to the admin group. There were also quite a few brute force hack on my SQL server and FTP server. I have blocked all IPs except for mine and things seems to be calming down these 2 days.

Have you heard of this Exploit-DFind before? I am not sure if I should do a server reload (Partly because I don't really want the server to go down for unknown hours because I am in the middle of a big advertising campaign). I hope no other system files were corrupted.

aspdaddy

10:53 am on Feb 17, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Most security efforts are amined at blocking stuff commig in. You have to accept that most web servers will get compromised at some point,and once that happens most the traffic will go the other way.

When deploying a web server just block any outbound ports you dont use to limit your liability.

Most web servers should never need to initiate an outbound session other than for AV/Windows updates etc, which are to known IP's, so you can pretty much block all outbound ports without losing any functionality.