Software

Ask something
Discussion Locked

Has the SQLsnake affected you?

0 helpful
2 replies

by debate

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Tell us what you think about the SQLsnake, as featured in the latest Internet Security Focus e-newsletter. Has your SQL Server 7 been affected by the worm? If so, how much damage has the worm done? Do you now have a strong password on your "sa" account?

2 replies

by rwblaas

Being an SQL Server DBA I follow up on all security aspects of SQL and Windows alike. As for this security issue none of the SQL's I manage or have installed have suffered. Neither do I know of any servers in my area that have been effected.

I believe that those who have taken the necessary basic steps will not have suffered. Those who have not followed up on MS's basic advise will have to quickly modify there settings (hoping it won't have a severe impact on operations) if it's not too late.

by jerry

My SQL Server is behind a firewall, and the only vulnerability was that we did have the sa password blank - this is because it is a test system, not production, and is used by multiple consultants.

Norton Anti-virus caught the virus last week, but I was unaware of actually being infected until I re-booted the server last Friday. When it came up, I had no network capability, except that I could still ping other machines. I could not see any other machines on the network, and could not see the server from any other machines.

I have done the recomended removal procedures from Norton, but it stated that there were some registry settings added or modified, but does not explain how to fix them!

It is network DDE related, on 2000 Server - I don't know if I can delete the registry key, or if I need to change the values to something else.

Any ideas?

This discussion is closed to new replies.