[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Multiple DNS implementations vulnerable to cache poisoning

Subject: Multiple DNS implementations vulnerable to cache poisoning
From: jfmezei at vaxination.ca (Jean-François Mezei)
Date: Wed, 09 Jul 2008 00:04:33 -0400
In-reply-to: <[email protected]>
References: <D0D0330CBD07114D85B70B784E80C2F2022FC9E8@exch-mail2.win.slac.stanford.edu> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]>

Re: the tool

My DNS server does not serve the outside world. Incoming packets to port
53 are NAT directed to an non-existant IP on the LAN.

The tool uses my internet facing IP as my DNS server and tells me I am
vulnerable. Since, from the internet, connecting to that IP at port 53
will not get you to a DNS server, I find the tool's conclusion rather
without much value.

Follow-Ups:
- Multiple DNS implementations vulnerable to cache poisoning
  - From: cmadams at hiwaay.net (Chris Adams)

References:
- Multiple DNS implementations vulnerable to cache poisoning
  - From: gtb at slac.stanford.edu (Buhrmaster, Gary)
- Multiple DNS implementations vulnerable to cache poisoning
  - From: jra at baylink.com (Jay R. Ashworth)
- Multiple DNS implementations vulnerable to cache poisoning
  - From: jra at baylink.com (Jay R. Ashworth)
- Multiple DNS implementations vulnerable to cache poisoning
  - From: shrdlu at deaddrop.org (Lynda)
- Multiple DNS implementations vulnerable to cache poisoning
  - From: owen at delong.com (Owen DeLong)
- Multiple DNS implementations vulnerable to cache poisoning
  - From: christian at broknrobot.com (Christian Koch)
- Multiple DNS implementations vulnerable to cache poisoning
  - From: mysidia at gmail.com (Jimmy Hess)

Prev by Date: Multiple DNS implementations vulnerable to cache poisoning
Next by Date: Multiple DNS implementations vulnerable to cache poisoning
Previous by thread: Multiple DNS implementations vulnerable to cache poisoning
Next by thread: Multiple DNS implementations vulnerable to cache poisoning
Index(es):
- Date
- Thread