Re: [Sip] draft-state-sip-relay-attack-00

Nils Ohlmeier <lists@ohlmeier.org> Fri, 06 March 2009 22:21 UTC

Return-Path: <lists@ohlmeier.org>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F9713A68AA for <sip@core3.amsl.com>; Fri, 6 Mar 2009 14:21:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level:
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ApcxVJxrut48 for <sip@core3.amsl.com>; Fri, 6 Mar 2009 14:21:00 -0800 (PST)
Received: from bespin.rfc3261.net (cl-395.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:18a::2]) by core3.amsl.com (Postfix) with ESMTP id 673C03A6825 for <sip@ietf.org>; Fri, 6 Mar 2009 14:21:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by bespin.rfc3261.net (Postfix) with ESMTP id EC89F7F82; Fri, 6 Mar 2009 23:21:28 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at bespin.rfc3261.net
Received: from bespin.rfc3261.net ([127.0.0.1]) by localhost (bespin.rfc3261.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFVFNdZt8-h0; Fri, 6 Mar 2009 23:21:28 +0100 (CET)
Received: from Nils-MacBook-2.local (unknown [78.52.228.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bespin.rfc3261.net (Postfix) with ESMTPSA id 675527F55; Fri, 6 Mar 2009 23:21:28 +0100 (CET)
Message-ID: <49B1A1E1.8070007@ohlmeier.org>
Date: Fri, 06 Mar 2009 23:21:21 +0100
From: Nils Ohlmeier <lists@ohlmeier.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; de; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To: Dale Worley <dworley@nortel.com>
References: <49AE593F.6080807@iptel.org> <e4c7495a3f98d5a2a85ccf85047515f0.squirrel@www.ohlmeier.com> <1236368519.3762.20.camel@victoria-pingtel-com.us.nortel.com>
In-Reply-To: <1236368519.3762.20.camel@victoria-pingtel-com.us.nortel.com>
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: sip@ietf.org
Subject: Re: [Sip] draft-state-sip-relay-attack-00
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2009 22:21:01 -0000

Am 06.03.2009 20:41 Uhr, schrieb Dale Worley:
> On Thu, 2009-03-05 at 14:40 +0100, Nils Ohlmeier wrote:
>> One thing which is not that obvious but is implictly a requirement for the
>> attack: the proxies has to challenge in-dialog requests. I do not see a
>> big benefit in challeging in-dialog requests as these are hopefully
>> rejected by the remote side if no matching dialog exists. If the UA would
>> know that his proxy does not challenge in-dialog requests it could simply
>> ignore the challenge :-)
>
> Except that there are legitimate uses for challenging in-dialog
> requests:  sipX uses it to allow a phone to transfer a caller to any
> destination that the executing phone has permission to call.  The first
> step of this process is that when the executing phone sends a REFER, the
> proxy challenges the REFER so that the executing phone attaches its
> credentials to the REFER.  The proxy then analyzes these credentials to
> determine the user that is responsible for the transfer operation, etc.
> Without the in-dialog challenge, there is no way for the proxy to
> determine the user that is responsible for transfer operation.

Good point. Except that a REFER is not relevant for this replay attack. 
So would re-phrase it: I do not see a big benefit in challeging 
in-dialog INVITE requests. :-)

Greetings
   Nils