Article View: comp.dcom.sys.cisco
Article #2258Re: IOS exploit: please disclose vehicle, not mechanism
From: jankemi(remove)
Date: Fri, 25 Jul 2003 01:21
Date: Fri, 25 Jul 2003 01:21
32 lines
2527 bytes
2527 bytes
Bill Johnston wrote: > > by noting in italics that: > > "ACLs can have performance impact on certain platforms, > so care should be taken when applying the recommended > workarounds." > We have input ACL's on our edge routers anyway, to block RFC1918 addresses & various other unwanted protocols. We added 3-4 more lines to those lists. I've always assumed that most organizations already have some kind of ingress ACL. Maybe not though? Our experience has been that ACL processing is not a major problem on our platforms (72xx's, 36xx's and 26xx's). > Not the information that I was asking for, Mike. You asked for the vehicle. I though that 'Multiple IPv4 packets with specific protocol fields sent directly to the device' was the vehicle. Perhaps you consider that the mechanism? > > Politely, my young man. > I'm not intending to be rude. If I'm short it's because I'm too lazy to type long messages. > - Bill
Technical Details
Message-ID:
<3F208459.6030804@mail.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!elnk-nf2-pas!newsfeed.earthlink.net!wn14feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi_feed4!attbi.com!rwcrnsc51.ops.asp.att.net.POSTED!not-for-mailReferences:
<Xns93C1BACF3C55Awdjohnstoncomcastnet@206.127.4.25> <LqFTa.116237$wk6.30285@rwcrnsc52.ops.asp.att.net> <Xns93C294B29ED49wdjohnstoncomcastnet@206.127.4.25>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f922c,536b22101f44acbf X-Google-Attributes: gidf922c,public X-Google-Thread: 102702,536b22101f44acbf X-Google-Attributes: gid102702,public X-Google-Thread: 114395,536b22101f44acbf X-Google-Attributes: gid114395,public X-Google-ArrivalTime: 2003-07-24 18:21:15 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!elnk-nf2-pas!newsfeed.earthlink.net!wn14feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi_feed4!attbi.com!rwcrnsc51.ops.asp.att.net.POSTED!not-for-mail Message-ID: <3F208459.6030804@mail.com> From: "jankemi(remove)" <"jankemi(remove)"@mail.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.dcom.sys.cisco,ios.general,comp.security.firewalls Subject: Re: IOS exploit: please disclose vehicle, not mechanism References: <Xns93C1BACF3C55Awdjohnstoncomcastnet@206.127.4.25> <LqFTa.116237$wk6.30285@rwcrnsc52.ops.asp.att.net> <Xns93C294B29ED49wdjohnstoncomcastnet@206.127.4.25> In-Reply-To: <Xns93C294B29ED49wdjohnstoncomcastnet@206.127.4.25> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Lines: 33 NNTP-Posting-Host: 24.245.5.3 X-Complaints-To: abuse@comcast.net X-Trace: rwcrnsc51.ops.asp.att.net 1059096074 24.245.5.3 (Fri, 25 Jul 2003 01:21:14 GMT) NNTP-Posting-Date: Fri, 25 Jul 2003 01:21:14 GMT Organization: Comcast Online Date: Fri, 25 Jul 2003 01:21:14 GMT