Re: [quicwg/base-drafts] Add initial threat model to security considerations (#2925)

Gorry Fairhurst <> Sat, 16 November 2019 04:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7758812007C for <>; Fri, 15 Nov 2019 20:58:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bsKzx6doCkme for <>; Fri, 15 Nov 2019 20:57:59 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EB79C1200B6 for <>; Fri, 15 Nov 2019 20:57:58 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id DBD8052098D for <>; Fri, 15 Nov 2019 20:57:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1573880277; bh=x2mmpvd90j+dIb3LHvx5e4B0BjplDhf2NWEDP2+BzyA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bMIi/6dKsOUdOSc85ztHyFktVqPjXh70PCUG2UkyNawYc6zWIEsCaDc6b0Vd/Ls2p vbGk7LYUNIhF2B5MgvYxa+Pok9eqpGRDewARVk9P42tjH3/NHHlX1oPyAknxjGVKQK 5wY2bzl8WjaxfWPMvR9XdN95cuxKQo6EstLj+ikQ=
Date: Fri, 15 Nov 2019 20:57:57 -0800
From: Gorry Fairhurst <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2925/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Add initial threat model to security considerations (#2925)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dcf81d5cc84c_7db53fa4294cd9682433150"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 16 Nov 2019 04:58:00 -0000

gorryfair commented on this pull request.

Comments from Hackathon - basically heading in correct direction.

> +to a new endpoint as part of an established QUIC connection.
+##### On-Path Active Attacks
+An attacker that can cause a packet it observes to no longer reach its intended
+destination is considered an on-path attacker.  Such an attacker generally is
+present between the QUIC client and server, and a QUIC endpoint is required to
+send packets through this attacker to establish connectivity on a given path.
+An on-path attacker can:
+- Inspect packets
+- Modify IP and UDP packet headers
+- Inject new packets
+- Delay packets

Delay (includes reordering)

> +the original path between endpoints, and therefore the original packets sent by
+an endpoint are still reaching their destination.  This means that a future
+failure to route copied packets to the destination faster than their original
+path will not prevent the original packets from reaching the destination.
+A limited on-path attacker can:
+- Inspect packets
+- Inject new packets
+- Modify unencrypted packet headers
+A limited on-path attacker cannot:
+- Delay packets beyond the original packet duration
+- Drop packets
+- Modify encrypted packet payloads

he can - but they don't work

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: