Re: [jose] JWS signature verification and claims payload

Les Hazlewood <lhazlewood@gmail.com> Thu, 12 October 2023 21:27 UTC

Return-Path: <lhazlewood@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF15FC151547 for <jose@ietfa.amsl.com>; Thu, 12 Oct 2023 14:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 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, FREEMAIL_FROM=0.001, 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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 iwVWzw7VrVS1 for <jose@ietfa.amsl.com>; Thu, 12 Oct 2023 14:27:32 -0700 (PDT)
Received: from mail-yw1-x1133.google.com (mail-yw1-x1133.google.com [IPv6:2607:f8b0:4864:20::1133]) (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 06384C151535 for <jose@ietf.org>; Thu, 12 Oct 2023 14:27:31 -0700 (PDT)
Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-59e88a28b98so12343597b3.1 for <jose@ietf.org>; Thu, 12 Oct 2023 14:27:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697146051; x=1697750851; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=qRwSw7xgH8d+eTBh+gBY0fkiQ38NF+2/w+NQ3ldCUPY=; b=e/xOb7Lw+oURUVv0Ik1FAATBJizGdiVeWBVU86KdCi5tWSh8fxVd8jQeTw6eLC7Y3J r0P2ptXg89xOWYK7KUnpEvn8Ln68MYWYpec9MZggP/Iu2aJaS6ZZktcHhvHXV0ITBZ89 kTIZ4n65/nnMtuVXzFnJCwPZ2porQtbls8STTBOJ9nkfKIMTm5tZU60lY3TS/3yggaum VTgtLF3aXyXc+ESUBcrSRgsquV3Ro6ioVu2p+h7LMw4R6GhUIAY48bvJuXQfYr1l+cSt oSDJagBHxXvz4HI9XW12bDBVlrn/W3/TwfpGDzGixKA9kv58kkqpciTGoGV6W3Ir5ZP8 fRaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697146051; x=1697750851; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=qRwSw7xgH8d+eTBh+gBY0fkiQ38NF+2/w+NQ3ldCUPY=; b=NG9b1EYpfKkS1wNke2q56TXiZIQAO1gATYlYtyOjzHm5LWpq04QsF3mdu83nYORTLs sn/upHLkPtGWZX036cYBxwEnA5cIKLdcTOXZy0k6ie3wF9fiYMSzTF0uIgOxIMb3E/QC 7s5i6UXOkE0mO+D24HQgTMbOaxT91Bhj6IYtvh/90c8lOVtVAnOvqKQtX8upYLyAxzlA Ie9jJcWIoxBc7re8TzdcOBCeJCE7805/PYDj2aTRHeRlJt7tu2sI5/Brpy5NAZXmpSE5 rMJDS25jAxGJCnQvgt1Fg6uZF9KKfteephkMcg/ZKXDKtpNw7STu6moWqjY5RygIAFdV GnNw==
X-Gm-Message-State: AOJu0Ywt8IYZGDDo6H/qgX34legVbi02SnMiEO8Ivk4Eb80sZzQELYTA sjJIWr4/Pg0TT9stBRlOKzHpxS+IdMvtDj3Z8rfa1zlNtfXzXQ==
X-Google-Smtp-Source: AGHT+IE4XELP1ZTqqojC+jEuKfqImec/flIuj4ackn0RE7CZJ9nRGgNvHePnNxNCWpE1zMQmU1yPt/XXvOgcLn70zoM=
X-Received: by 2002:a81:6c92:0:b0:5a7:ba3e:d1d1 with SMTP id h140-20020a816c92000000b005a7ba3ed1d1mr5775884ywc.25.1697146050736; Thu, 12 Oct 2023 14:27:30 -0700 (PDT)
MIME-Version: 1.0
References: <CACVbtYO28BkxPXoXKUojjV_XFGQOEV7EDs=d1TZ9ymcBhFicUQ@mail.gmail.com> <CAN8C-_L68Pay8nVjSxbjGo_q3kyggp1P-5_iruOaFPCsy5dw0Q@mail.gmail.com> <CACVbtYO+xOiXiYaZZ-+kspSAmxLHw0UKohmG-GksLT5Kcjsw=A@mail.gmail.com> <CAN8C-_Jz5o9OO19eb2WG3iJfNcFKm2mN1eeD--Qy0bi3Y=nmxA@mail.gmail.com>
In-Reply-To: <CAN8C-_Jz5o9OO19eb2WG3iJfNcFKm2mN1eeD--Qy0bi3Y=nmxA@mail.gmail.com>
From: Les Hazlewood <lhazlewood@gmail.com>
Date: Thu, 12 Oct 2023 14:27:19 -0700
Message-ID: <CACVbtYM1WXFqN8o4BnAH0SS=t+wttWF30gAqj+XK_6vh2dZWhQ@mail.gmail.com>
To: jose@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007c75e206078b9b52"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/TIvr2FPetPKk4Ma1QIf0gNdAAIs>
Subject: Re: [jose] JWS signature verification and claims payload
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Oct 2023 21:27:35 -0000

>
> Yep, I agree with you but see my comments on "alg none" below.
>

Unprotected JWTs (alg == "none") aren't the issue here. I'm explicitly
asking about whether the payload may be parsed before signature
verification when any algorithm other than "none" is in the header.

I think this answers your second question:
>
> https://datatracker.ietf.org/doc/html/rfc7519#section-7.2
>

That section defers to my original link
https://datatracker.ietf.org/doc/html/rfc7515#section-5.2 in the JWS RFC.
Both RFC 7519 and RFC 7515 state in the numerically ordered sequence:

"The order of the steps is not significant in cases where there are
no dependencies between the inputs and outputs of the steps."

There is no dependency on the payload for signature verification, so any
parsing of it to a JSON object before signature verification is omitted in
both RFCs.  That just means it's not _required_.  Neither RFC states
whether it's actually allowed.  (Interestingly, Base64URL-decoding is not
required for signature verification either, but that *is* explicitly listed
in the ordered steps).

Could anyone from the RFC committee please clarify the RFC intent for this
scenario given the security implications?

Kind regards,

Les