From: Amir Herzberg <amir.herzberg@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>,
Haya Shulman <haya.shulman@gmail.com>
Subject: Re: Resolver behind NetFilter NAT service vulnerable to DNS poisoning attack
Date: Thu, 2 Sep 2010 17:06:57 +0200 [thread overview]
Message-ID: <AANLkTimoL4yDha_iMKtHRFSaLQcf=xeYp1cF=qySAz_D@mail.gmail.com> (raw)
In-Reply-To: <1283436292.2454.790.camel@edumazet-laptop>
Eric, thanks. I'm sorry for forgetting to mention this before, but the
attack I referred to was against NAT _using_ port randomization, i.e.
--random option (Netfilter from 2.4).
We did _not_ refer to the known attack against NAT using
port-preserving option (i.e., without port randomization). This attack
is trivial when the DNS is not using port randomization, and we also
show how to do this when the DNS is using port randomization. But the
more challenging attack is when the NAT is using port randomization
(--random). Of course, we also explain how to prevent these attacks.
Cheers, Amir and Haya
On Thu, Sep 2, 2010 at 4:04 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Le jeudi 02 septembre 2010 à 15:50 +0200, Amir Herzberg a écrit :
>> We investigate some issues related to DNS poisoning, and specifically,
>> an attack that poisons DNS cache, similar to Kaminski's attack, but
>> that works even if the resolver selects random ports, as long as
>> resolver is connected to the Internet via NAT. In particular, we
>> tested the attack for the NetFilter NAT.
>>
>> For obvious reasons, I prefer at this point to share details only with
>> developers of NAT devices. If you are such developer, please contact
>> me and I can send you the details (paper).
>> Feel also welcome to forward the messages to individuals/forums which
>> may be relevant (i.e., developers).
>>
>> I apologize for not being able to promise to respond to requests from
>> people who are just curious (i.e., not NAT developers). Thanks for
>> your understanding.
>> --
>
> Strange, this should be supported since 2007 (port randomization for
> nat)
>
> commit 41f4689a7c8cd76b77864461b3c58fde8f322b2c
> Author: Eric Leblond <eric@inl.fr>
> Date: Wed Feb 7 15:10:09 2007 -0800
>
> [NETFILTER]: NAT: optional source port randomization support
>
> This patch adds support to NAT to randomize source ports.
>
> Signed-off-by: Eric Leblond <eric@inl.fr>
> Signed-off-by: Patrick McHardy <kaber@trash.net>
> Signed-off-by: David S. Miller <davem@davemloft.net>
>
> If using MASQUERADE, its a very easy setup :
>
> iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE --random
>
>
>
>
--
Amir Herzberg
Associate Professor, Dept. of Computer Science
Bar Ilan University
http://AmirHerzberg.com
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-09-02 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikjFnoh_=PX7YDv18O46JhLFnyXQ9-f2CEumqRd@mail.gmail.com>
2010-09-02 13:50 ` Resolver behind NetFilter NAT service vulnerable to DNS poisoning attack Amir Herzberg
2010-09-02 14:04 ` Eric Dumazet
2010-09-02 15:06 ` Amir Herzberg [this message]
2010-09-02 18:24 ` Amir Herzberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimoL4yDha_iMKtHRFSaLQcf=xeYp1cF=qySAz_D@mail.gmail.com' \
--to=amir.herzberg@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=haya.shulman@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).