full-disclosure - rumours of new Cisco IOS vulnerability

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20030717010752.GJ4584@netsys.com>
From: len at netsys.com (Len Rose)
Subject: rumours of new Cisco IOS vulnerability

Yes, that's exactly what you should do. Don't forget any
of the loopback addresses as well. The question is what
code trains are vulnerable, and what will folks with older
hardware be able to do about it if Cisco says "no fix".

Len

On Wed, Jul 16, 2003 at 02:45:45PM -0700, Blue Boar wrote:

[snippage]

> That generally means packets with a destination address of one of the 
> router's own interfaces.  If there's some mystery exploit out there, one 
> workaround would be to firewall the router's own IP address(es).  This 
> would still allow the router to perform its routing function for other IPs.
>