Re: [OAUTH-WG] Mix-Up and CnP/ Code injection

Daniel Fett <fett@uni-trier.de> Tue, 10 May 2016 08:23 UTC

Return-Path: <prvs=931d7fcc2=fett@uni-trier.de>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4506F12D1D4 for <oauth@ietfa.amsl.com>; Tue, 10 May 2016 01:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.196
X-Spam-Level:
X-Spam-Status: No, score=-5.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
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 AKBynWi36bLn for <oauth@ietfa.amsl.com>; Tue, 10 May 2016 01:23:42 -0700 (PDT)
Received: from mx1.uni-trier.de (mx1.uni-trier.de [136.199.224.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70CE712B074 for <oauth@ietf.org>; Tue, 10 May 2016 01:23:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.24,604,1454972400"; d="scan'208";a="20212894"
Received: from rzmail.uni-trier.de ([136.199.8.220]) by mx1i.uni-trier.de with ESMTP; 10 May 2016 10:23:40 +0200
Received: from [136.199.52.39] (infsec39.uni-trier.de [136.199.52.39]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by rzmail.uni-trier.de (Postfix) with ESMTPSA id 96AF7409C4; Tue, 10 May 2016 10:23:40 +0200 (CEST)
To: oauth@ietf.org
References: <571B60BA.8090301@lodderstedt.net> <572B56BB.9080903@uni-trier.de> <CABzCy2DB8yy9yJBzjEKmLu5gHf=ZPsnj20=iBV2JkbeY9VLu9A@mail.gmail.com>
From: Daniel Fett <fett@uni-trier.de>
Message-ID: <57319A8C.3070408@uni-trier.de>
Date: Tue, 10 May 2016 10:23:40 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CABzCy2DB8yy9yJBzjEKmLu5gHf=ZPsnj20=iBV2JkbeY9VLu9A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/MSshH4hay4Rd8wM45IQ299kW5u8>
Subject: Re: [OAUTH-WG] Mix-Up and CnP/ Code injection
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 08:23:45 -0000

It does not work if the AS does not check the redirect URI completely.
Facebook being the main example here, and I guess they won't change this
soon (for backwards compatibility). Adding the iss parameter won't break
things.

-Daniel

Am 09.05.2016 um 05:45 schrieb Nat Sakimura:
> Hi Daniel, 
> 
> May I ask again why separate redirect uri would not work for mix-up? 
> (I know, it does not work for cut-n-paste.) 
> 
> Thanks, 
> 
> Nat
> 
> 2016年5月5日(木) 23:28 Daniel Fett <fett@uni-trier.de
> <mailto:fett@uni-trier.de>>:
> 
>     Am 23.04.2016 um 13:47 schrieb Torsten Lodderstedt:
>     > I'm very much interested to find a solution within the OAuth realm as
>     > I'm not interested to either implement two solutions (for OpenId
>     Connect
>     > and OAuth) or adopt a OpenId-specific solution to OAuth (use id!
>     tokens
>     > in the front channel). I therefore would like to see progress and
>     > propose to continue the discussion regarding mitigations for both
>     threats.
>     >
>     > https://tools.ietf.org/html/draft-ietf-oauth-mix-up-mitigation-00
>     > proposes reasonable mitigations for both attacks. There are
>     alternatives
>     > as well:
>     > - mix up:
>     > -- AS specific redirect uris
>     > -- Meta data/turi
>     > (https://tools.ietf.org/html/draft-sakimura-oauth-meta-07#section-5)
>     > - CnP:
>     > -- use of the nonce parameter (as a distinct mitigation beside
>     state for
>     > counter XSRF)
> 
>     >From our formal analysis of OAuth we are pretty confident that the
>     mitigation proposed in draft-ietf-oauth-mix-up-mitigation-00 should be
>     sufficient against the Mix-Up attack.
> 
>     Cheers,
>     Daniel
> 
> 
>     --
>     Informationssicherheit und Kryptografie
>     Universität Trier - Tel. 0651 201 2847 - H436
> 
>     _______________________________________________
>     OAuth mailing list
>     OAuth@ietf.org <mailto:OAuth@ietf.org>
>     https://www.ietf.org/mailman/listinfo/oauth
> 
> -- 
> Nat Sakimura
> Chairman of the Board, OpenID Foundation
> Trustee, Kantara Initiative


-- 
Informationssicherheit und Kryptografie
Universität Trier - Tel. 0651 201 2847 - H436