NSS client will sign CertificateVerify message with rsa_pkcs1_sha256 SignatureScheme in TLS 1.3
Categories
(NSS :: Libraries, defect, P1)
Tracking
(firefox-esr60 wontfix, firefox67 wontfix, firefox68 fixed, firefox69 fixed)
People
(Reporter: hkario, Assigned: ueno)
References
Details
(Keywords: sec-low, Whiteboard: [post-critsmash-triage][adv-main68+])
Attachments
(2 files)
It's possible to force NSS client to sign CertificateVerify with PKCS#1 v1.5 signatures when those are the only ones advertised by server in CertificateRequest.
tested with nss-4.34.0
packet capture with SSLKEYLOGFILE attached
| Reporter | ||
Comment 1•6 years ago
|
||
typo; I've tested with nss-3.43.0
Comment 2•6 years ago
|
||
Is this a "vulnerability" that needs to be hidden, or an edge-case bug for people who configure their servers wrong?
Comment 3•6 years ago
|
||
This does look like a spec compliance issue, as PKCS1-v1_5 signatures should not be used for TLS 1.3 messages. It's supposed to be allowed to be advertised for 1.2 backwards compat, and of course used in x.509.
I don't think this has serious security impacts -- I suppose it's another avenue for Bleichenbacker, but if only on a single message, it's probably sec-low/sec-other? :mt, can you weigh in on that?
Adding CryptoEng staff for visibility.
Updated•6 years ago
|
Comment 4•6 years ago
|
||
Yes, we should filter out PKCS1-v1_5. We didn't originally because we started out with no PSS, but that isn't a good reason to keep it that way.
| Assignee | ||
Comment 5•6 years ago
|
||
| Assignee | ||
Comment 6•6 years ago
|
||
Comment 7•6 years ago
|
||
Is this something we should consider backporting to 3.44 so it's included in Fx68 (and by extension, our next ESR)?
Updated•6 years ago
|
Comment 8•6 years ago
|
||
Probably yes. Daiki, if you agree, feel free to do the backport. Otherwise, I'll add transplanting it to my todo list for the next week or so
| Assignee | ||
Comment 9•6 years ago
|
||
Sure, pushed to 3.44: https://hg.mozilla.org/projects/nss/rev/17c6fc2ec3c1feaed56ef59b35bf435c7d5c4949
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•5 years ago
|
Description
•