From: Daniel Borkmann <dborkman@redhat.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, Harald Welte <laforge@gnumonks.org>
Subject: Re: [PATCH nf] netfilter: nf_nat: fix buffer overflow in IRC NAT helper
Date: Mon, 06 Jan 2014 14:09:53 +0100 [thread overview]
Message-ID: <52CAAB21.1080703@redhat.com> (raw)
In-Reply-To: <20140106130444.GA8155@localhost>
On 01/06/2014 02:04 PM, Pablo Neira Ayuso wrote:
> Hi Daniel,
>
> On Tue, Dec 31, 2013 at 04:28:39PM +0100, Daniel Borkmann wrote:
>> diff --git a/net/netfilter/nf_nat_irc.c b/net/netfilter/nf_nat_irc.c
>> index f02b360..fbbb1e6 100644
>> --- a/net/netfilter/nf_nat_irc.c
>> +++ b/net/netfilter/nf_nat_irc.c
>> @@ -34,10 +34,14 @@ static unsigned int help(struct sk_buff *skb,
>> struct nf_conntrack_expect *exp)
>> {
>> char buffer[sizeof("4294967296 65635")];
>> + struct nf_conn *ct = exp->master;
>> + union nf_inet_addr newaddr;
>> u_int16_t port;
>> unsigned int ret;
>>
>> /* Reply comes from server. */
>> + newaddr = ct->tuplehash[IP_CT_DIR_REPLY].tuple.dst.u3;
>> +
>> exp->saved_proto.tcp.port = exp->tuple.dst.u.tcp.port;
>> exp->dir = IP_CT_DIR_REPLY;
>> exp->expectfn = nf_nat_follow_master;
>> @@ -57,17 +61,41 @@ static unsigned int help(struct sk_buff *skb,
>> }
>>
>> if (port == 0) {
>> - nf_ct_helper_log(skb, exp->master, "all ports in use");
>> + nf_ct_helper_log(skb, ct, "all ports in use");
>> return NF_DROP;
>> }
>>
>> - ret = nf_nat_mangle_tcp_packet(skb, exp->master, ctinfo,
>> - protoff, matchoff, matchlen, buffer,
>> - strlen(buffer));
>> + /* strlen("\1DCC CHAT chat AAAAAAAA P\1\n")=27
>> + * strlen("\1DCC SCHAT chat AAAAAAAA P\1\n")=28
>> + * strlen("\1DCC SEND F AAAAAAAA P S\1\n")=26
>> + * strlen("\1DCC MOVE F AAAAAAAA P S\1\n")=26
>> + * strlen("\1DCC TSEND F AAAAAAAA P S\1\n")=27
>> + *
>> + * AAAAAAAAA: bound addr (1.0.0.0==16777216, min 8 digits,
>> + * 255.255.255.255==4294967296, 10 digits)
>> + * P: bound port (min 1 d, max 5d (65635))
>> + * F: filename (min 1 d )
>> + * S: size (min 1 d )
>> + * 0x01, \n: terminators
>> + */
>> + /* AAA = "us", ie. where server normally talks to. */
>> + if (nf_ct_l3num(ct) == NFPROTO_IPV4) {
>> + snprintf(buffer, sizeof(buffer), "%u %u",
>> + ntohl(newaddr.ip), port);
>> + pr_debug("nf_nat_irc: inserting '%s' == %pI4, port %u\n",
>> + buffer, &newaddr.ip, port);
>> + } else {
>> + nf_ct_helper_log(skb, ct, "IPv6 DCC unsupported for now");
>> + return NF_DROP;
>> + }
>
> I have mangled your patch (see attachment) to remove this branch since
> there is real IPv6 support for IRC yet in master. We'll need to
> revisit this anyway when finishing IPv6 support to the IRC helper. Let
> me know if you have any concern with this. Thanks.
Thanks, that's fine.
+ * 0x01, \n: terminators
+ */
+ /* AAA = "us", ie. where server normally talks to. */
+ snprintf(buffer, sizeof(buffer), "%u %u", ntohl(newaddr.ip), port);
+ pr_debug("nf_nat_irc: inserting '%s' == %pI4, port %u\n",
+ buffer, &newaddr.ip, port);
That should be good for now. The thing I've noticed so far is that for
DCC and IPv6 there doesn't seem to be a standard and clients try to
parse "%u %u" and expect IPv4 here.
But anyway, that fixes the bug, feel free to apply, thanks.
+ ret = nf_nat_mangle_tcp_packet(skb, ct, ctinfo, protoff, matchoff,
+ matchlen, buffer, strlen(buffer));
prev parent reply other threads:[~2014-01-06 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 15:28 [PATCH nf] netfilter: nf_nat: fix buffer overflow in IRC NAT helper Daniel Borkmann
2013-12-31 17:29 ` Pablo Neira Ayuso
2013-12-31 17:35 ` Pablo Neira Ayuso
2014-01-01 4:13 ` Daniel Borkmann
2013-12-31 17:42 ` Hannes Frederic Sowa
2014-01-06 13:04 ` Pablo Neira Ayuso
2014-01-06 13:09 ` Daniel Borkmann [this message]
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=52CAAB21.1080703@redhat.com \
--to=dborkman@redhat.com \
--cc=laforge@gnumonks.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).