Re: SQL slammer, i have it, awww geez now what?
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 07/23/04
- Next message: TOM P.: "Re: adding windows user via sp_cmdshell"
- Previous message: Birdy: "SQL slammer, i have it, awww geez now what?"
- In reply to: Birdy: "SQL slammer, i have it, awww geez now what?"
- Next in thread: Peter: "SQL slammer, i have it, awww geez now what?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 23 Jul 2004 08:55:43 -0400
It doesn't matter how it was installed you need to run the patches or latest
services packs and that will take care of it.
-- Andrew J. Kelly SQL MVP "Birdy" <anonymous@discussions.microsoft.com> wrote in message news:285d01c47083$8052c030$a601280a@phx.gbl... > the tool removal and bulletins say it's for MSDE, but > mine is installed thru an application (no vendor does not > have fix) and mine says MSDA and JET 4.0 and is OLEDB > Provider for ODBC drivers (MSDTC) I shut down ports > 1433 and 1434 and 26101 and 35894 (last two are > backdoors). but i am clueless on what to do about > patches. i really don't use SQL except thru how my > application calls on it to do it's job. i am getting > buffer overflow and DoS. ouch.
- Next message: TOM P.: "Re: adding windows user via sp_cmdshell"
- Previous message: Birdy: "SQL slammer, i have it, awww geez now what?"
- In reply to: Birdy: "SQL slammer, i have it, awww geez now what?"
- Next in thread: Peter: "SQL slammer, i have it, awww geez now what?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
