Slammer Worm/SQL Server 7

From: Ricky Artigas (rya@easycall.com.ph)
Date: 02/21/03 

From: "Ricky Artigas" <rya@easycall.com.ph>
Date: Fri, 21 Feb 2003 11:19:23 -0800

SQL Server 7 is not affected by the Slammer worm because
it doesn't use port 1434 for the name resolution. SQL
Server 7 is not like SQL Server 2k which can run more
than one instance of SQL Server on the same machine and
it uses 1434 for some sort of named instance resolution.

HTH.

>-----Original Message-----
>We are using SQL Server 7.0 , Service Pack 3. Is there
>any risk from the Slammer Worm that we need to be
worried
>about? I saw a remark on the PASS website that SQL
Server
>7.0 was not at risk from the Slammer Worm but appears to
>be subject to the same vulnerability?
>
>Thanks.
>.
>

Relevant Pages

  • Re: Slammer Worm/SQL Server 7
    ... No risk from Slammer as SQL7 does not support named ... Service in which the buffer overflow exploited by Slammer ... > any risk from the Slammer Worm that we need to be worried ... I saw a remark on the PASS website that SQL Server ...
    (microsoft.public.sqlserver.security)
  • Slammer Worm/SQL Server 7
    ... any risk from the Slammer Worm that we need to be worried ... I saw a remark on the PASS website that SQL Server ...
    (microsoft.public.sqlserver.security)
  • Re: Why does sql 2000 scream to the world ... how do you shut this thing up?
    ... SQL Server 7 is not affected by the slammer worm. ... Resolution Service which is used by SQL Server 2000 to ... that's just life on the internet I'm afraid. ...
    (microsoft.public.sqlserver.security)
  • Re: SQL server
    ... I feel that your SQL server is affected with Slammer Worm. ... rapidly spreading computer worm infects networks and bogs ... Did you apply the SP3 for SQL Server, ...
    (microsoft.public.sqlserver.security)
  • Slammer Worm/SQL Server 7
    ... SQL Server 7 is not affected by the Slammer worm because ... it uses 1434 for some sort of named instance resolution. ... >7.0 was not at risk from the Slammer Worm but appears to ...
    (microsoft.public.sqlserver.security)