full-disclosure - SQL Slammer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20030210162620.60F97113769@percivale>
From: vdongen at hetisw.nl (I.R. van Dongen)
Subject: SQL Slammer - lessons learned


> Huh?  Our IDSes detect both Code Red I, II and III and Nimda every day,
> as does my Wormcatcher.  I don't know *anyone* who is blocking port 80.
> Do you?
accually, the rotterdam area of chello ISP blocks port 80.
They started blocking that when code red 1 almost took their internal network down.
Which meanth for *nix users, that first came the flood of requests that came with code red, then their port 80 was suddenly unreachable.
So instead of warning non-patching users, they block all users.

> 
> Paul Schmehl (pauls@...allas.edu)
> Adjunct Information Security Officer
> The University of Texas at Dallas
> http://www.utdallas.edu/~pauls/
> AVIEN Founding Member 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
> 
>