[secdir] secdir review of draft-ietf-avtcore-ports-for-ucast-mcast-rtp-01

Charlie Kaufman <charliek@microsoft.com> Wed, 06 April 2011 04:14 UTC

Return-Path: <charliek@microsoft.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 7F61C3A6860; Tue, 5 Apr 2011 21:14:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id ipjmvfEiryfb; Tue, 5 Apr 2011 21:14:43 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com []) by core3.amsl.com (Postfix) with ESMTP id B9D383A685B; Tue, 5 Apr 2011 21:14:43 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com ( by TK5-EXGWY-E803.partners.extranet.microsoft.com ( with Microsoft SMTP Server (TLS) id; Tue, 5 Apr 2011 21:16:27 -0700
Received: from TK5EX14MBXC110.redmond.corp.microsoft.com ([]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([]) with mapi id 14.01.0270.002; Tue, 5 Apr 2011 21:16:27 -0700
From: Charlie Kaufman <charliek@microsoft.com>
To: "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-avtcore-ports-for-ucast-mcast-rtp.all@tools.ietf.org" <draft-ietf-avtcore-ports-for-ucast-mcast-rtp.all@tools.ietf.org>
Thread-Topic: secdir review of draft-ietf-avtcore-ports-for-ucast-mcast-rtp-01
Thread-Index: AcvzxmoOwCr5HXG7TFutkMKEhgYPyg==
Date: Wed, 06 Apr 2011 04:16:27 +0000
Message-ID: <D80EDFF2AD83E648BD1164257B9B09122C41462A@TK5EX14MBXC110.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [secdir] secdir review of draft-ietf-avtcore-ports-for-ucast-mcast-rtp-01
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2011 04:14:44 -0000

I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.

This protocol deals with requesting and managing multicast and unicast connection streams, and in particular dealing with the case where they are coming through a NAT. The interesting security threat in this case is one of DoS through amplification, where the attacker with a small number of packets can request that a source direct a large number of packets towards the victim. Because these streams do not have the sorts of acknowledgements that would force a TCP stream to back off if the target were unresponsive, the possibility of this sort of attack is particularly dangerous.

The RTP and RTCP protocols have no authentication infrastructure that can be leveraged. There is a resumption that all information is public and can be requested by any destination. (It is possible that one could implement encryption at a higher layer such that the data received would not be useful to someone who doesn't know the key, but any such encryption is beyond the scope of this protocol). This means that certain security attacks are unavoidable. In particular, an attacker could potentially exhaust the source or the network by requesting that data from large numbers of locations simultaneously. And an attacker that can act as a man-in-the-middle between source and victim can initiate a flood of data and then get out of the way.

This protocol attempts to assure that an attacker that can forge the victim's IP address but cannot receive packets addressed to the victim cannot mount an amplification DoS attack. It does that by adding a "token" to various messages in the protocol. The token is generated by the source when a context is set up and must be supplied by the receiver in requests to modify the data streams. In order to not add state at the source, they recommend that the token be generated as an HMAC-SHA1 of the concatenation of the client IP address, a client nonce (that is chosen for the session and supplied with each request), and a server timestamp (also chosen per session and supplied to prevent long delayed replay). This closely matches the design of "cookies" in other protocols.

The recommended use of HMAC-SHA1 may be slightly controversial, but its security is more than adequate for this application, it is a local decision on the part of the server, and the I-D has excellent text on how and when implementations should migrate to a different algorithm (in particular, referencing HMAC-SHA2-256).

There is one aspect of the design that I could not figure out reading the spec, and it would seem to relate to a security vulnerability that the spec therefore does not close. The spec recommends computing the token as a hash over a number of fields including the source IP address but not the source port. It appears that this is because the RTP and RTCP protocols use different ports and they want to use the same token with both. This introduces a threat, however, that if a node requests a token, that token will be valid for all nodes that are NATted behind the same IP address. An attacker in the inside of the NATted network could therefore acquire a token, hand it off to a co-conspirator outside the NATted network, and that co-conspirator could use it to direct traffic at a different node inside the network. It's not obvious what could or should be done to mitigate this threat. The spec allows for - but recommends against - using lots of different ports on the client side for different purposes, but I couldn't figure out how the client knows how all of those ports will be translated by the NAT. If there were a separate token per port, this problem could be solved, but I suspect there is some reason why that is impractical.