Re: [quicwg/base-drafts] handling of coalesced packets with decryption errors creates DoS opportunity (#2308)

Christian Huitema <notifications@github.com> Thu, 09 May 2019 04:11 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 41F1B120266 for <quic-issues@ietfa.amsl.com>; Wed, 8 May 2019 21:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Level:
X-Spam-Status: No, score=-1.464 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 0pRyRoai0g2S for <quic-issues@ietfa.amsl.com>; Wed, 8 May 2019 21:11:05 -0700 (PDT)
Received: from o10.sgmail.github.com (o10.sgmail.github.com [167.89.101.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1327D12002E for <quic-issues@ietf.org>; Wed, 8 May 2019 21:11:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=xwKUzcLcmGAxgb3eOEZcko0NEwE=; b=DzBrT+m4bDObH5JI /aMrUU3bdTjhkQPMcDowx08EoWgowmXN4JPEGiMohRYT7y/BXxY7hIhhnBEQ6hos 3ZAst4HbaLzYUwceKFWEOoFUQC+yAB1H7QNf2B45sMxMQTK7aSIjv7WytLrBT61g Oh/5XHP4liLfiE+ot/ggQLXOJ04=
Received: by filter1426p1mdw1.sendgrid.net with SMTP id filter1426p1mdw1-20282-5CD3A857-2D 2019-05-09 04:11:03.985070259 +0000 UTC m=+25386.297116203
Received: from github-lowworker-6313c1a.cp1-iad.github.net (unknown [140.82.115.7]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id vADrcRd8SKqE1Yxi-InVfg for <quic-issues@ietf.org>; Thu, 09 May 2019 04:11:03.955 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-6313c1a.cp1-iad.github.net (Postfix) with ESMTP id D9AE2380087 for <quic-issues@ietf.org>; Wed, 8 May 2019 21:11:03 -0700 (PDT)
Date: Thu, 09 May 2019 04:11:04 +0000
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7W2RWH25EL3QP6H5F24DNNPEVBNHHBPH547M@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2308/490736116@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2308@github.com>
References: <quicwg/base-drafts/issues/2308@github.com>
Subject: Re: [quicwg/base-drafts] handling of coalesced packets with decryption errors creates DoS opportunity (#2308)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd3a857d613b_4e7b3fd4946cd95c64332"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak19UtW5Tc01o8AWEm8yx1XwWntqUDCRGX28Qg FmiG6pqM6drBCzLTftYpSzulM7YRoT9b11zd1KG0oMhD7bdffunuKv8S/m2slncXVACdlL7nrBRS9B kCB3YiNIUIOUx1+zCZ1Zm3EpULT1IXmNONUgNKRIMMX4TYsZWXuKwp5Q8vY7mk4lGXF/yH+ljl3z/P g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/-D2oFnj5DW_nTR8PMqb7QwqMPMw>
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: Thu, 09 May 2019 04:11:07 -0000

I am a bit skeptical of the idea of using coalesced packets for PMTU discovery. If I receive a handshake packet after the handshake is finished, I will most probably ignore it. I don't have the keys anymore, I cannot remove header protection or packet protection. Packet will be treated as a decryption error, and whatever is coalesced with it will most likely be ignored.

I understand the goal of coalescing is to find a CID in the ICMP payload, but that seems somewhat brittle. Parsing the ICMP based on the 5 tuple would be much more robust, and does not require playing games with packet coalescing.

I may be a bit biased because I would rather just completely ignore all ICMP packets, and rely only on end-to-end ACKs. It removes the need to find a portable way to obtain ICMP messages through the socket API, and it also prevents attacks by ICMP spoofing.

-- 
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/2308#issuecomment-490736116