full-disclosure - Re: DNS Cache Dan Kamikaze (Actual Exploit Discussion)

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

Message-ID: <4ef5fec60807131515w1e1e0da0u7c793e7733592fe0@mail.gmail.com>
Date: Sun, 13 Jul 2008 15:15:37 -0700
From: coderman <coderman@...il.com>
To: "eugaaa@...il.com" <eugaaa@...il.com>
Cc: full-disclosure@...ts.grok.org.uk,
	Paul Schmehl <pschmehl_lists_nada@...rr.com>
Subject: Re: DNS Cache Dan Kamikaze (Actual Exploit
	Discussion)

On Sun, Jul 13, 2008 at 2:27 PM, eugaaa@...il.com <eugaaa@...il.com> wrote:
> ...
> So on that note I'll be more direct. Has anyone actually preemptively
> written any code or reversed this issue on their own? Or just, you
> know, attempted to understand the vulnerability in detail instead of
> relying on these intentionally vague advisories (dan)?

my money is currently on ICMP port unreachable combined with the
predictable ports to trick vulnerable resolvers into thinking the
configured nameservers are offline:

http://wari.mckay.com/~rm/dns_theroy.txt

you could fix this via the method described, and not imply that the
ICMP was part of the vector.

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/