|
|||||||||||
|
Re: SQLSlammer Worm & IDSs
From: Mike Barkett <mbarkett(at)nfr.com>
Date: Wed Jan 29 2003 - 18:31:54 EST Andrew - Prior even to the initial propagation of the worm, NFR NID detected exploitation of the underlying vulnerability and identified it as a "SQL Server stack overflow." Several major NFR customers sent us emails complimenting us on our foresight, as their NFR NID appliances have enabled them to detect this attack since August, 2002. Still, our Rapid Response Team responded the day of the outbreak, releasing an updated version of the package that indentified the worm by its new name and included some tuning variables to help reduce the number of alerts generated by the incoming onslaught from other, more vulnerable sites. From my perspective, this was remarkably reminiscent of the Nimda epidemic, and it is another testament to the value of advanced hybrid intrusion detection solutions. -MAB
-----BEGIN PGP SIGNED MESSAGE-----
I am curious what people were seeing with SQL Slammer and their IDSs. I've been collecting anecdotal evidence that Slammer flew right past a lot of IDSs. I know that Snort and BlackICE just reported UDP port probes. Snort got a sig early Saturday morning however. RealSecure sensors had a signature in September that seemed to worked. I am curious what anybody running Cisco's IDS, Symantec Manhunt, Enterasys Dragon, NFR, Intruvert, or any other IDS saw. Was it identified as a worm or just a port probe? What has me concerned is that the smallness of this worm made it look like nothing more than a UDP probe. As such, a lot of IDSs didn't consider this a very important event, since a UDP port probe is a pretty common event on any network. Andrew Plato, CISSP President / Principal Consultant Anitian Corporation 503-644-5656 Office 503-644-8574 Fax 503-201-0821 Mobile www.anitian.com -----BEGIN PGP SIGNATURE-----
iD8DBQE+NwjfRFTPAXEeGWkRAoYjAJ9YQ4Y5zrWtbukdw1sAp2bhyFkoIACfZkdl
ev2MhAeNBwJaoTEXZDG+/mk==cGis
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:01:08 EDT |
||||||||||
|
|||||||||||