Re: [OAUTH-WG] OAuth security BCP: Lifetime of authorization codes
Jeff Craig <jeffcraig@google.com> Wed, 21 September 2022 15:56 UTC
Return-Path: <jeffcraig@google.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 4C9EFC14CE24 for <oauth@ietfa.amsl.com>; Wed, 21 Sep 2022 08:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -22.608
X-Spam-Level:
X-Spam-Status: No, score=-22.608 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2WkqGLkUEhe for <oauth@ietfa.amsl.com>; Wed, 21 Sep 2022 08:56:41 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4888C14F735 for <oauth@ietf.org>; Wed, 21 Sep 2022 08:56:41 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id n81so5398343iod.6 for <oauth@ietf.org>; Wed, 21 Sep 2022 08:56:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=VR/+wJ1vn/3/gyt0tTiGwLSoLbPdJloeST5mGsyRwvE=; b=ow8Zac/jUZlVmHPh23XKvJmIcK5glfyiWtDpLH+QvZErGr4MXiET85EjPsuRFTbVnA 0iIIpx5wB0qcwB8siUe57PwPigZ5IdyO/dSg3u/h0Ow8TkZCgecoMFSx52Jhk1gqQ/aM BKxZy9252VmYxLEugcAxTCHjpXrXcBJmpMS2vNaknYpZYwiU3Ba2PWeDtUIiF7wRj94A lLWjxTBQtPSevVJtY9L6doyjLfuRM7W9+uQGmsOZxuZCnMNkQBHx9dmJPsfjH4lNkExp NUoQoydsqZGNnW8RCSpfm8n3yS8NsLXTYG6VN7aIu7vEcC2u/OFv3OhdskZ0hqWCwl3U Jxsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=VR/+wJ1vn/3/gyt0tTiGwLSoLbPdJloeST5mGsyRwvE=; b=lrWvSztUBUpPJHDnlS9QCrbtqSvuVsRloNi9OfjKeQFAz2BPShMsjNsStW21WJrk2E QeQXBBNajx6WrO8gFFDRTYOdiSmKKlbhQGj6/1U5n/h75ml3kXcWqsb+liidqOH+0YQZ qjtV/GJyusljG6BvomBHBKF86h/CdAbGtTMIKE/s+AwL7h//cxwwWyGCmUChD8X+rUwI NOk4ji+fcnqekdQx/tYh4gHIRVicrbVCar/yiqmEiseVtNfNX9QqhO0tiQ4DnL+j06iw +SIK21r/IHdLUSBLHEYIgN/uzIG/Kpxmb4kX6l6Z9CMJCulWDONt9q8y5W0kEp9oZuGc UTjw==
X-Gm-Message-State: ACrzQf18j5KlznL+8KRQcHG5fv1yailruzzfrSSiz01ZYDnOoTcVy/su IXqyboCDEpY+fT/bsz2SNlKFq5oZiPULyXYbdpVJSNDfA7jsRA==
X-Google-Smtp-Source: AMsMyM4CclFeRR65wHVdEXLrtnq1o+Qebdgj35viQ4fIsKMDW1LxQIqHzYTBWMNoCh2FZe4FlgFsnbDmClZpsRQR9J8=
X-Received: by 2002:a05:6638:339c:b0:35a:28d4:2189 with SMTP id h28-20020a056638339c00b0035a28d42189mr13462512jav.176.1663775800428; Wed, 21 Sep 2022 08:56:40 -0700 (PDT)
MIME-Version: 1.0
References: <588F53CC-2E58-47C6-A777-3BBB91412BFF@authlete.com>
In-Reply-To: <588F53CC-2E58-47C6-A777-3BBB91412BFF@authlete.com>
From: Jeff Craig <jeffcraig@google.com>
Date: Wed, 21 Sep 2022 08:56:29 -0700
Message-ID: <CAKhDPzMTcynt5dWH_WMCH-30CJcZfPF4vK0moNFXTja0nG-_-w@mail.gmail.com>
To: Joseph Heenan <joseph@authlete.com>
Cc: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000927ef205e931fd03"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/5Ifq7iMTiBT9F4xHB_shQpLUpiI>
Subject: Re: [OAUTH-WG] OAuth security BCP: Lifetime of authorization codes
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 21 Sep 2022 15:56:42 -0000
Re-use of Authorization Codes is a strict violation of the spec as described in https://datatracker.ietf.org/doc/html/rfc6749#section-4.1.2 I generally agree that a shorter lifetime is fine in most cases, but the lifetime of the authorization code is not what provides security, the single-use requirement does. On Wed, Sep 21, 2022 at 1:39 AM Joseph Heenan <joseph@authlete.com> wrote: > Hi all > > I couldn't find any text in the current BCP document about the lifetime of > authorization codes, do people think that this may be worth mentioning? > > The only guidance I could find on authorization code lifetimes is RFC > 6749, 4.1.2: > > "A maximum authorization code lifetime of 10 minutes is RECOMMENDED.” > > Feedback from some vendors (on the FAPI WG) seemed to be that they default > to shorter lifetimes these days. > > Shorter lifetimes seem like they can prevent various attacks, particularly > if the AS isn't enforcing single-use of authorization code. > > > (I raised this at > https://github.com/oauthstuff/draft-ietf-oauth-security-topics/issues/50 too, > but forgot to email this list at the time) > > Thanks > > Joseph > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
- [OAUTH-WG] OAuth security BCP: Lifetime of author… Joseph Heenan
- Re: [OAUTH-WG] OAuth security BCP: Lifetime of au… Jeff Craig