[PLUG] Latest round of Microsoft insecurity

Anthony Schlemmer aschlemm at attbi.com
Tue May 21 20:19:08 UTC 2002


Thanks for posting this...Now I know why my firewall is being pounded on 
port 1433. I knew the port was for SQL Server but I guess I wasn't 
really that concerned since it's against my Linux firewall.

Tony

On Tuesday 21 May 2002 13:01 pm, Stafford A. Rau wrote:
> Don't let your friends run M$ SQL Server (M-Squeal-Server) on an
> unprotected host, if at all. Scanning for default or no password SQL
> accounts, which lead to full system compromise, is running rampant
> right now:
>
>
> May  9 19:06:10 kort tcplogd: port 1433 connection attempt from
> [193.15.48.103] May 20 11:21:30 kort tcplogd: port 1433 connection
> attempt from [198.182.98.6] May 20 11:21:30 kort tcplogd: port 1433
> connection attempt from [198.182.98.6] May 20 11:21:30 kort tcplogd:
> port 1433 connection attempt from [198.182.98.6] May 20 16:35:07 kort
> tcplogd: port 1433 connection attempt from [203.184.168.130] May 20
> 16:35:11 kort tcplogd: port 1433 connection attempt from
> [203.184.168.130] May 20 18:29:37 kort tcplogd: port 1433 connection
> attempt from [203.116.179.22] May 20 18:29:38 kort tcplogd: port 1433
> connection attempt from [203.116.179.22] May 20 18:29:38 kort
> tcplogd: port 1433 connection attempt from [203.116.179.22] May 20

[snip]

-- 
Anthony Schlemmer
aschlemm at attbi.com
>>>>This machine was last rebooted:   1 days 23:39 hours ago<<





More information about the PLUG mailing list