From: Roberto Nibali <ratz@drugphish.ch>
To: Martin Renold <martinxyz@gmx.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] tcp connection tracking 2.4.19
Date: Tue, 08 Oct 2002 23:06:55 +0200 [thread overview]
Message-ID: <3DA348EF.7060709@drugphish.ch> (raw)
In-Reply-To: 20021008205053.GA2621@old.homeip.net
Hello Martin,
> There is a bug in the stable 2.4.19 kernel in the ip_conntrack code that
> allows the final ACK of a SYN - SYN/ACK - ACK tcp handshake to establish
> an ASSURED connection even if it has a wrong sequence number. The current
> code only checks the ACK number.
Yes, and more than that. You can remove ESTABLISHED entries in the
conntrack table by sending packets with the RST flag set and matching
the template <srcIP, srcPORT, dstIP, dstPORT>.
> This allows a DoS attack that will make it impossible to establish *real*
> connections for some days, once the maximum is reached. Somebody sent me
> an exploit:
:) You should probably send stuff like that to the netfilter-devel ml.
Besides that it isn't really an exploit.
> http://old.homeip.net/martin/cdos.tgz
>
> So I wrote a simple patch against 2.4.19, but I must admit that I do not
> really understand the code around it, especially why it does not mark
> such a packet as invalid (I'm new to most things here).
You might want to take a look at the TCP window tracking patch which
comes with the latest pom. It's part of the extra patches. This will
solve the problems for you.
> diff -urN -X dontdiff kernel-source-2.4.19.origin/net/ipv4/netfilter/ip_conntrack_proto_tcp.c kernel-source-2.4.19.patch/net/ipv4/netfilter/ip_conntrack_proto_tcp.c
> --- kernel-source-2.4.19.origin/net/ipv4/netfilter/ip_conntrack_proto_tcp.c Fri Oct 4 08:13:38 2002
> +++ kernel-source-2.4.19.patch/net/ipv4/netfilter/ip_conntrack_proto_tcp.c Sat Oct 5 20:45:49 2002
> @@ -180,6 +180,8 @@
> if (oldtcpstate == TCP_CONNTRACK_SYN_SENT
> && CTINFO2DIR(ctinfo) == IP_CT_DIR_REPLY
> && tcph->syn && tcph->ack)
> + conntrack->proto.tcp.handshake_seq
> + = tcph->ack_seq;
> conntrack->proto.tcp.handshake_ack
> = htonl(ntohl(tcph->seq) + 1);
> WRITE_UNLOCK(&tcp_lock);
> @@ -196,6 +198,7 @@
> if (oldtcpstate == TCP_CONNTRACK_SYN_RECV
> && CTINFO2DIR(ctinfo) == IP_CT_DIR_ORIGINAL
> && tcph->ack && !tcph->syn
> + && tcph->seq == conntrack->proto.tcp.handshake_seq
> && tcph->ack_seq == conntrack->proto.tcp.handshake_ack)
> set_bit(IPS_ASSURED_BIT, &conntrack->status);
>
Welcome to the world of almost-stateful packet filtering. Hey, other
than that, the 3wahas 'exploit' is old. Also don't I understand why they
claim that SYN cookies prevent syn flooding. Next time you meet someone
of the guys, tell them about the backlog queue.
Cheers,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next prev parent reply other threads:[~2002-10-08 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 20:50 [patch] tcp connection tracking 2.4.19 Martin Renold
2002-10-08 21:06 ` Roberto Nibali [this message]
2002-10-09 12:30 ` Gianni Tedesco
2002-10-09 17:25 ` Roberto Nibali
2002-10-10 10:38 ` Gianni Tedesco
2002-10-10 18:06 ` Roberto Nibali
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=3DA348EF.7060709@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=martinxyz@gmx.ch \
/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