diff options
author | Matt Caswell <matt@openssl.org> | 2021-03-25 10:20:50 +0000 |
---|---|---|
committer | Matt Caswell <matt@openssl.org> | 2021-03-25 13:12:42 +0000 |
commit | 468d9d556409a53da2c5d16961f9531dd10a6e1b (patch) | |
tree | f63c695e506f406bcdd5e400beee8a9f0aea863f /CHANGES.md | |
parent | 39a140597d874e554b736885ac4dea16ac40a87a (diff) |
Update CHANGES.md and NEWS.md for new release
Reviewed-by: Tomas Mraz <tomas@openssl.org>
Diffstat (limited to 'CHANGES.md')
-rw-r--r-- | CHANGES.md | 43 |
1 files changed, 43 insertions, 0 deletions
diff --git a/CHANGES.md b/CHANGES.md index 559f09a035..c57b9ad4a5 100644 --- a/CHANGES.md +++ b/CHANGES.md @@ -1661,6 +1661,49 @@ OpenSSL 1.1.1 ### Changes between 1.1.1j and 1.1.1k [xx XXX xxxx] + * Fixed a problem with verifying a certificate chain when using the + X509_V_FLAG_X509_STRICT flag. This flag enables additional security checks of + the certificates present in a certificate chain. It is not set by default. + + Starting from OpenSSL version 1.1.1h a check to disallow certificates in + the chain that have explicitly encoded elliptic curve parameters was added + as an additional strict check. + + An error in the implementation of this check meant that the result of a + previous check to confirm that certificates in the chain are valid CA + certificates was overwritten. This effectively bypasses the check + that non-CA certificates must not be able to issue other certificates. + + If a "purpose" has been configured then there is a subsequent opportunity + for checks that the certificate is a valid CA. All of the named "purpose" + values implemented in libcrypto perform this check. Therefore, where + a purpose is set the certificate chain will still be rejected even when the + strict flag has been used. A purpose is set by default in libssl client and + server certificate verification routines, but it can be overridden or + removed by an application. + + In order to be affected, an application must explicitly set the + X509_V_FLAG_X509_STRICT verification flag and either not set a purpose + for the certificate verification or, in the case of TLS client or server + applications, override the default purpose. + ([CVE-2021-3450]) + + *Tomáš Mráz* + + * Fixed an issue where an OpenSSL TLS server may crash if sent a maliciously + crafted renegotiation ClientHello message from a client. If a TLSv1.2 + renegotiation ClientHello omits the signature_algorithms extension (where it + was present in the initial ClientHello), but includes a + signature_algorithms_cert extension then a NULL pointer dereference will + result, leading to a crash and a denial of service attack. + + A server is only vulnerable if it has TLSv1.2 and renegotiation enabled + (which is the default configuration). OpenSSL TLS clients are not impacted by + this issue. + ([CVE-2021-3449]) + + *Peter Kästle and Samuel Sapalski* + ### Changes between 1.1.1i and 1.1.1j [16 Feb 2021] * Fixed the X509_issuer_and_serial_hash() function. It attempts to |