Metasploit mailing list archives

bailiwicked_domain not working anymore?


From: richard.k.miles at googlemail.com (Richard Miles)
Date: Mon, 20 Jul 2009 20:49:52 -0500

Hi Paolo and HD,

You are right, the server fail to solve the red subdomain. :/

If I'm doing things correctly, the source port is not static, it have
small increments. So in this case Metasploit is unable to exploit it?

thanks guys

On Mon, Jul 20, 2009 at 1:28 PM, HD Moore<hdm at metasploit.com> wrote:
On Mon, 20 Jul 2009 10:09:54 -0500, Paolo Milani <j.s.sebastian at gmail.com>
wrote:

I presume that the server for the red subdomain should then reply
putting the port number used by the server in the TXT section.

Unfortunately this server is down (in fact, the red subdomain does not
resolve)."

I should have it back up soon, just forgot about it :-)

Since sending back the src port of the server in the TXT section is not
standard DNS behavior, and the code for this server doesn't seem to have
been released, even if you set up your own authoritative server the
check functionality will still not work.

There is a DNS server module with the same functionality as the
red.metasploit.com domain under auxiliary/server/dns/spoofhelper

Richard Miles wrote:

Both servers show to be vulnerable, similar to this one output:


porttest.y.x.w.v.u.t.s.r.q.p.o.n.m.l.k.j.i.h.g.f.e.d.c.b.a.pt.dns-oarc.net.
"myDNSserver is POOR: 26 queries in 1.9 seconds from 26 ports with std
dev 7"


This indicates a weak port distribution, but not a static port, which the
metasploit module requires to work.

-HD
_______________________________________________
https://mail.metasploit.com/mailman/listinfo/framework



Current thread: