IETF Logo Mail Archive

Re: [OAUTH-WG] Call for Feedback on draft-ietf-oauth-iss-auth-resp-00

Neil Madden <neil.madden@forgerock.com> Mon, 10 May 2021 12:57 UTC

Return-Path: <neil.madden@forgerock.com>
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 AA76A3A1BDD for <oauth@ietfa.amsl.com>; Mon, 10 May 2021 05:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forgerock.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 RjsIW1NKhCoL for <oauth@ietfa.amsl.com>; Mon, 10 May 2021 05:57:42 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 629C63A1BDA for <oauth@ietf.org>; Mon, 10 May 2021 05:57:42 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id h4so16506686wrt.12 for <oauth@ietf.org>; Mon, 10 May 2021 05:57:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forgerock.com; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=JXfOUbqZDFWYgkpVlkTT1kv/+4TK21bdiFwRfKottAk=; b=XgnwnmNp5wuqUen+p8Hbz7trwAQw/C3JMkq+Ylmz2P9BXBdqveMxHRhY4Z859V74qs Ly6I0h3EI3O7o5AskvPH46hi40d0fQHk87tGa+mXXKkhxxMwEr2k4gwgK3ECMBr/4Iic +o7pZXADe8aIOt/3Wyj/YZp6YHZK6MHywL4kg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=JXfOUbqZDFWYgkpVlkTT1kv/+4TK21bdiFwRfKottAk=; b=ElI/43SUp+yIKleUjkVZmWNoMPAle6eim0bMgQtO6jj/U+EULsCjuzOBLtTPp4Hg9y vpCZoyApvE2pNAaLdAYxbVLO9zoopDw1wpIlmqyFcUDMjA0e6WLqlvUG7jWTfMslLZrG IbzSQuPFncFerUoHazhBdhfT9dA2YQIZDc2qsCICGeFl25N1rZIB8LPG5LHfvDUUx6sd niFKuiKTVLP4Z9mOe7k2/oC3T0PPYIMVpb7a3KgmsznCKsoUlgg2SScGHzBs2+QZOFQ5 CcbpIIXCD+E6UCfplNJmTKn2Evk2WvL5d1GAqP85AnHlu3Lek4/fpUvbCZzpaW2THd2E ro+Q==
X-Gm-Message-State: AOAM531H4p1Kc7Y75W1uMYAx3eWp+yB3zkG1p+cmS54RtnR6PXL9LwfJ z5vXHxsrxKq/OLGsPdfVslj5I1OYgmWBI3nOMH4jL9I2yfS6TT4XNuvjMlCnZQVU7EOasnQWeA= =
X-Google-Smtp-Source: ABdhPJzJatFKCFmxeAsmTUKixATkCuIvqNPsFFx+zjwTtC+CD3jcT4zcSbqKcJ3JWuz4yvuFICVN+g==
X-Received: by 2002:adf:e70b:: with SMTP id c11mr31233291wrm.196.1620651459894; Mon, 10 May 2021 05:57:39 -0700 (PDT)
Received: from [10.0.0.8] (252.207.159.143.dyn.plus.net. [143.159.207.252]) by smtp.gmail.com with ESMTPSA id s15sm22182221wrt.19.2021.05.10.05.57.39 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 May 2021 05:57:39 -0700 (PDT)
From: Neil Madden <neil.madden@forgerock.com>
Message-Id: <E43CA16C-CB38-4E9E-9ADD-295ECBA38ED9@forgerock.com>
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.6\))
Date: Mon, 10 May 2021 13:57:38 +0100
In-Reply-To: <634f7b10-bb26-e05c-7d79-566c893c32b6@hackmanit.de>
Cc: oauth <oauth@ietf.org>
To: Karsten Meyer zu Selhausen <karsten.meyerzuselhausen@hackmanit.de>
References: <634f7b10-bb26-e05c-7d79-566c893c32b6@hackmanit.de>
X-Mailer: Apple Mail (2.3608.120.23.2.6)
Content-Type: multipart/alternative; boundary="Apple-Mail=_3167FA58-077B-4E35-BFBE-A5C22F0F09A6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/9sRGjGyBFUDfTPZkrA9qQTGTUL0>
Subject: Re: [OAUTH-WG] Call for Feedback on draft-ietf-oauth-iss-auth-resp-00
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 May 2021 12:57:48 -0000

I have also read it and it looks good to me. It might be worth explicitly discussing how it relates to the older draft [1] (that we implemented at the time). That older draft also included a client_id parameter in the response, so it would be good to clarify if that is actually needed to prevent the attack or not.

[1]: https://datatracker.ietf.org/doc/html/draft-ietf-oauth-mix-up-mitigation-01 <https://datatracker.ietf.org/doc/html/draft-ietf-oauth-mix-up-mitigation-01> 

Kind regards,

Neil

> On 15 Apr 2021, at 08:04, Karsten Meyer zu Selhausen <karsten.meyerzuselhausen@hackmanit.de> wrote:
> 
> Hi all,
> 
> the latest version of the security BCP references draft-ietf-oauth-iss-auth-resp-00 as a countermeasures to mix-up attacks.
> 
> There have not been any concerns with the first WG draft version so far: https://datatracker.ietf.org/doc/draft-ietf-oauth-iss-auth-resp/ <https://datatracker.ietf.org/doc/draft-ietf-oauth-iss-auth-resp/>
> I would like to ask the WG if there are any comments on or concerns with the current draft version.
> 
> Otherwise I hope we can move forward with the next steps and hopefully finish the draft before/with the security BCP.
> 
> Best regards,
> Karsten
> 
> -- 
> Karsten Meyer zu Selhausen
> Senior IT Security Consultant
> Phone:	+49 (0)234 / 54456499
> Web:	https://hackmanit.de <https://hackmanit.de/> | IT Security Consulting, Penetration Testing, Security Training
> 
> Is your OAuth or OpenID Connect client vulnerable to the severe impacts of mix-up attacks? Learn how to protect your client in our latest blog post on single sign-on:
> https://www.hackmanit.de/en/blog-en/132-how-to-protect-your-oauth-client-against-mix-up-attacks <https://www.hackmanit.de/en/blog-en/132-how-to-protect-your-oauth-client-against-mix-up-attacks>
> 
> Hackmanit GmbH
> Universitätsstraße 60 (Exzenterhaus)
> 44789 Bochum
> 
> Registergericht: Amtsgericht Bochum, HRB 14896
> Geschäftsführer: Prof. Dr. Jörg Schwenk, Prof. Dr. Juraj Somorovsky, Dr. Christian Mainka, Dr. Marcus Niemietz
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth


-- 
ForgeRock values your Privacy <https://www.forgerock.com/your-privacy>

v2.23.0 | Report a Bug | By Email