WebCrypto Design issue for AES GCM
Reported by
antonio....@gmail.com,
Jul 30
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: Instant Demo in https://asanso.github.io/firefox/aesgcm.html What is the expected behavior? What went wrong? IMHO the Webcrypto API has a design issue (at least in the AES GCM case). As you might see from the code in https://asanso.github.io/firefox/aesgcm.html I have created a wrapping key that has only ["wrapKey" ] usage. It should not be possible to recover back the aeskey using ["unwrapKey" ]. This is indeed the case. But given the fact the Webcrypto API allow to pass an explicit IV it is trivial in the AES GCM to recover back the aes key using "wrapKey" again. See https://cryptosense.com/blog/attacks-on-key-wrapping-in-pkcs11-v2-40/ for the equivalent issue in the HSM case. Did this work before? N/A Does this work in other browsers? No Chrome version: 67.0.3396.99 Channel: n/a OS Version: OS X 10.13.3 Flash Version:
,
Jul 30
(Restricting as requested.)
,
Jul 30
Thanks @agl . Whoever will take this might also want to change the component to Blink - WebCrypo (As was my original plan before screwing things up :S)
,
Jul 30
,
Jul 30
,
Jul 30
> Does this work in other browsers? No Note that this is not specific to Chrome - other implementations (including Firefox) work this way, since the spec lets the user control the IV used during encryption.
,
Jul 31
@eroman Yeah I know. As said above this bug was not ready to be filed. For some reason I clicked submit too early. Of course you are right about Firefox. I reported as well to them and they already filed https://github.com/w3c/webcrypto/issues/209
,
Jul 31
Ah understood! I will defer the design question to Ryan then. The W3C bug tracker is probably the better place to continue that discussion.
,
Aug 13
Hi guys, it would be great to hear some opinion.... :)
,
Aug 13
Marking as WontFix, to continue discussion upstream.
,
Aug 13
Thanks a lot Ryan. It would actually be great get your opinion (here or upstream is the same :))
,
Nov 19
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by antonio....@gmail.com
, Jul 30