Re: [Full-Disclosure] SQL Slammer - lessons learned

From: David LaPorte (david_laporte@harvard.edu)
Date: 02/10/03

  • Next message: petard@hushmail.com: "Re: [Full-Disclosure] SQL Slammer - lessons learned"
    From: David LaPorte <david_laporte@harvard.edu>
    To: "Schmehl, Paul L" <pauls@utdallas.edu>
    Date: Mon, 10 Feb 2003 10:23:08 -0500
    

    Not sure if this is dated (I'm not an AT&T customer), but AT&T was filtering
    port 80 as a result of Code Red. This document leads me to believe it will
    continue indefinately.

    http://help.broadband.att.com/faq.jsp?content_id=792&category_id=54 <em>&gt; &gt; for queries to a &quot;destination&quot; u> >Code Red/Nimda have fizzled out (probably still some infected

    (you need to choose your state and choose Broadband Internet)

    David

    On Monday 10 February 2003 09:48, Schmehl, Paul L wrote:
    > -----Original Message-----
    > From: John.Airey@rnib.org.uk [mailto:John.Airey@rnib.org.uk]
    > Sent: Monday, February 10, 2003 4:24 AM
    > To: guninski@guninski.com; Schmehl, Paul L
    > Cc: full-disclosure@lists.netsys.com
    > Subject: RE: [Full-Disclosure] SQL Slammer - lessons learned
    >
    > >Code Red/Nimda have fizzled out (probably still some infected
    > >machines out there), since it is possible to block ports below
    > >1024.
    >
    > 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?
    >
    > Paul Schmehl (pauls@utdallas.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

    -- 
    David LaPorte, CISSP
    Senior Network Security Engineer
    Harvard University Information Services NOC
    -----------------------------------------------
    Email: david_laporte@harvard.edu
      PGP: 0x4DC3E508
           4A1F058DB2B32FEF10A14F6BD370A6AD4DC3E508
    _______________________________________________
    Full-Disclosure - We believe in it.
    Charter: http://lists.netsys.com/full-disclosure-charter.html
    


    Relevant Pages

    • Re: AW: [Full-Disclosure] GROUP CONSIDERING SUIT AGAINST MICROSOFT OV ER SLAMMER VIRUS
      ... time hinted strongly at port 1434 being an issue to be dealt with. ... > recall was made, ... > Full-Disclosure - We believe in it. ... > Charter: http://lists.netsys.com/full-disclosure-charter.html ...
      (Full-Disclosure)
    • Re: worlds largest BDSM community
      ... Every testy map or port, ... It spreaded, you holded, yet Taysseer never rightly practised ... on behalf of the charter. ... These days, foots initiate upon nineteenth-century ...
      (alt.talk.royalty)
    • RE: [Full-Disclosure] Blocking Music Sharing.
      ... another port simply rate limit the traffic on a border router to ... | To: Dimitri Limanovski; Johnson, ... | Subject: Re: [Full-Disclosure] Blocking Music Sharing. ... | Charter: http://lists.netsys.com/full-disclosure-charter.html ...
      (Full-Disclosure)
    • Re: Back again...
      ... So I switched to Charter. ... As it was with this last problem with Usenet News. ... I mention port 119, or nntp and they glaze over and fall-back to same ... Error reported by Server: 400-Too many connections. ...
      (rec.woodworking)
    • Re: [Full-disclosure] CSIS Advisory: BlueCoat K9 Web Protection 3.2.36 Overflow
      ... K9 Web Protection local Web configuration manager on 127.0.0.1 and port ... Full-Disclosure - We believe in it. ... Charter: http://lists.grok.org.uk/full-disclosure-charter.html ...
      (Full-Disclosure)