1864262 - ECDH JWK imports should not be checking the JWK "alg" parameter

Status: RESOLVED DUPLICATE of bug 1905120

(Core :: DOM: Web Crypto, defect, P5)

Description

[Filip Skokan]

Steps to reproduce:

const publicJwk = {
kty: 'EC',
crv: 'P-256',
alg: 'THIS CAN BE ANYTHING',
x: 'Ze2loSV3wrroKUN_4zhwGhCqo3Xhu1td4QjeQ5wIVR0',
y: 'HlLtdXARY_f55A3fnzQbPcm6hgr34Mp8p-nuzQCE0Zw',
}

await crypto.subtle.importKey('jwk', publicJwk, { name: 'ECDH', namedCurve: 'P-256' }, true, [])

Actual results:

importKey is rejected with "Data provided to an operation does not meet requirements"

Expected results:

The key should successfully import, ECDH JWK key import steps do not have a step for checking the JWK alg. This is a problem for when ECDH is used as a step in fully specified JOSE Algorithms such as the upcoming HPKE-Base-P256-SHA256-AES128GCM and other HPKE based algorithms, or even the existing ones such as ECDH-ES or ECDH-ES+A128KW

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:keeler, could you have a look please?

For more information, please visit BugBot documentation.