From owner-cvs-all Sun Dec 17 9:21: 2 2000 From owner-cvs-all@FreeBSD.ORG Sun Dec 17 09:20:59 2000 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 7A0BA37B400; Sun, 17 Dec 2000 09:20:58 -0800 (PST) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 0A3443E4A; Sun, 17 Dec 2000 18:20:57 +0100 (CET) Date: Sun, 17 Dec 2000 18:20:56 +0100 From: Jesper Skriver To: "Louis A. Mamakos" Cc: Kris Kennaway , Poul-Henning Kamp , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, security-officer@FreeBSD.ORG Subject: Re: cvs commit: src/sys/netinet ip_icmp.c tcp_subr.c tcp_var.h Message-ID: <20001217182056.B34282@skriver.dk> References: <200012161942.eBGJg7j93654@freefall.freebsd.org> <20001217012007.A18038@citusc.usc.edu> <200012171529.eBHFT4512582@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200012171529.eBHFT4512582@whizzo.transsys.com>; from louie@TransSys.COM on Sun, Dec 17, 2000 at 10:29:04AM -0500 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 17, 2000 at 10:29:04AM -0500, Louis A. Mamakos wrote: > > On Sat, Dec 16, 2000 at 11:42:07AM -0800, Poul-Henning Kamp wrote: > > > phk 2000/12/16 11:42:07 PST > > > > > > Modified files: > > > sys/netinet ip_icmp.c tcp_subr.c tcp_var.h > > > Log: > > > We currently does not react to ICMP administratively prohibited > > > messages send by routers when they deny our traffic, this causes > > > a timeout when trying to connect to TCP ports/services on a remote > > > host, which is blocked by routers or firewalls. > > > > This sounds like a security hole since ICMP messages don't have a TCP > > sequence number meaning they can be trivially spoofed - am I wrong? > > The Destination Unreachable ICMP message should include a copy of the > IP header plus 20 bytes of payload (TCP segment header) which you > could use to validate it. I only glanced briefly at the patch, and don't > know if that was being done or not. It doesn't, from what I could read, we only get the IP header, so what was committed only looks at the protocol (make sure it's TCP) and source/ destination ip address, and zap's all matching TCP sessions in SYN-SENT state. > At that point, the situation is essentially the same as a RST-based > attack and trying to predict TCP sequence numbers. Agree, will look more at this, and see if we can the tcp source and destination port numbers. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message