full-disclosure - modifying shadowchode exploit

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: <20030720002618.GF506@spoofed.org>
From: warchild at spoofed.org (Jon Hart)
Subject: modifying shadowchode exploit

On Sat, Jul 19, 2003 at 04:52:06PM -0400, Ben Matlock wrote:
> I took a look at the output of the released Cisco exploit and added 2 lines 
> to make it generate random payload.  More could be done.
> 
> Ben

I haven't heard anywhere that the packets needed to exploit this
vulnerability need _any_ payload, much less a specific one.  This is the
reason that the IDS signatures that have been generated so far do not
alert on any specific payloads but just alert on the specific protocols.
Yes, such signatures can be noisey, but this all depends on your network
setup and can be tweaked accordingly.  There still seems to be some
confusion of whether or not the TTL must be 0/1 when it lands at the
target.  If and when that is confirmed, the signatures could be tweaked
more.  However, I'm not sure alerting *only* when the protocol is one of
the 4 and the TTL is 0 or 1 is the right thing.  

-jon