diff options
author | Jack Lloyd <[email protected]> | 2020-07-05 14:05:46 -0400 |
---|---|---|
committer | Jack Lloyd <[email protected]> | 2020-07-05 14:05:46 -0400 |
commit | b25aafa41385b3521c5157a01e0a33828eed3269 (patch) | |
tree | 523785e750f7348698928aa466d42bbe6a8b86df | |
parent | 9c4bf9476b5ee6272f04b2622ad2a0687b56b362 (diff) |
Update news
-rw-r--r-- | doc/security.rst | 13 | ||||
-rw-r--r-- | news.rst | 24 |
2 files changed, 37 insertions, 0 deletions
diff --git a/doc/security.rst b/doc/security.rst index e2e736a91..3a2059879 100644 --- a/doc/security.rst +++ b/doc/security.rst @@ -18,6 +18,19 @@ https://keybase.io/jacklloyd and on most PGP keyservers. 2020 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +* 2020-07-05: Failure to enforce name constraints on alternative names + + The path validation algorithm enforced name constraints on the primary DN + included in the certificate but failed to do so against alternative DNs which + may be included in the subject alternative name. This would allow a corrupted + sub-CA which was constrained by a name constraints extension in its own + certificate to issue a certificate containing a prohibited DN. Until 2.15.0, + there was no API to access these alternative name DNs so it is unlikely that + any application would make incorrect access control decisions on the basis of + the incorrect DN. Reported by Mario Korth of Ruhr-Universität Bochum. + + Introduced in 1.11.29, fixed in 2.15.0 + * 2020-03-24: Side channel during CBC padding The CBC padding operations were not constant time and as a result would leak @@ -4,10 +4,32 @@ Release Notes Version 2.15.0, Not Yet Released ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +* Fix a bug where the name constraint extension did not constrain the + alternative DN field which can be included in a subject alternative name. This + would allow a corrupted sub-CA which was otherwise constrained by a name + constraint to issue a certificate with a prohibited DN. + +* Fix a bug in the TLS server during client authentication where where + if a (disabled by default) static RSA ciphersuite was selected, then + no certificate request would be sent. This would have an equivalent + effect to a client which simply replied with an empty Certificate + message. (GH #2367) + * Replace the T-Tables implementation of AES with a 32-bit bitsliced version. As a result AES is now constant time on all processors. (GH #2346 #2348 #2353 #2329 #2355) +* In TLS, enforce that the key usage given in the server certificate + allows the operation being performed in the ciphersuite. (GH #2367) + +* In X.509 certificates, verify that the algorithm parameters are + the expected NULL or empty. (GH #2367) + +* Change the HMAC key schedule to attempt to reduce the information + leaked from the key schedule with regards to the length of the key, + as this is at times (as for example in PBKDF2) sensitive information. + (GH #2362) + * Add Processor_RNG which wraps RDRAND or the POWER DARN RNG instructions. The previous RDRAND_RNG interface is deprecated. (GH #2352) @@ -25,6 +47,8 @@ Version 2.15.0, Not Yet Released * When building documentation using Sphinx avoid parallel builds with version 3.0 due to a bug in that version (GH #2326 #2324) +* Fix a memory leak in the CommonCrypto block cipher calls (GH #2371) + * Fix a flaky test that would occasionally fail when running the tests with a large number of threads. (GH #2325 #2197) |