Re: [quicwg/base-drafts] Spoofed connection migration as a DoS vector (#2342)

Martin Thomson <notifications@github.com> Mon, 21 January 2019 04:56 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 941E212D4F2 for <quic-issues@ietfa.amsl.com>; Sun, 20 Jan 2019 20:56:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.935
X-Spam-Level:
X-Spam-Status: No, score=-10.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ddu_zR1hfNm for <quic-issues@ietfa.amsl.com>; Sun, 20 Jan 2019 20:56:21 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF3FF12867A for <quic-issues@ietf.org>; Sun, 20 Jan 2019 20:56:20 -0800 (PST)
Date: Sun, 20 Jan 2019 20:56:19 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548046579; bh=O4GKMyrc3B0zQvThL+MsbqTFTiDigKLYOdhkQCit47U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EJ9Lpyd1nbFm2izej8N7V/C71OrLJDvaCKKyMesN29b6pd/vVFaewwFCEjphlW17/ qKQ/O7G3LOicfP3vH4aVBX1iOSMfDF8GkedcXtCBAPDCvWQCLp9QVDNHUD7ISUAlFB orUmVY9ztD7+Ap2Sk7MTOulabSdvw047N6OkJPag=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab91b7e3acf3858db9821240135e93327a2d01740392cf00000001185d12f392a169ce17dd73ed@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2342/455948414@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2342@github.com>
References: <quicwg/base-drafts/issues/2342@github.com>
Subject: Re: [quicwg/base-drafts] Spoofed connection migration as a DoS vector (#2342)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c4550f3b5a46_aab3fb9f9ed45c0567ac"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/RfuPhjg3BvgM7cBlT8QOWDbN5d8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2019 04:56:22 -0000

Yeah, that seems like too simple a DoS.

It sort of highlights the need to implement much of the migration machinery if you consider the risk of NAT rebinding.  Unless you plan to only permit remote address changes based on a "same network" heuristic.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2342#issuecomment-455948414