|
7 | 7 | https://github.com/openssl/openssl/commits/ and pick the appropriate
|
8 | 8 | release branch.
|
9 | 9 |
|
| 10 | + Changes between 1.1.1j and 1.1.1k [25 Mar 2021] |
| 11 | + |
| 12 | + *) Fixed a problem with verifying a certificate chain when using the |
| 13 | + X509_V_FLAG_X509_STRICT flag. This flag enables additional security checks |
| 14 | + of the certificates present in a certificate chain. It is not set by |
| 15 | + default. |
| 16 | + |
| 17 | + Starting from OpenSSL version 1.1.1h a check to disallow certificates in |
| 18 | + the chain that have explicitly encoded elliptic curve parameters was added |
| 19 | + as an additional strict check. |
| 20 | + |
| 21 | + An error in the implementation of this check meant that the result of a |
| 22 | + previous check to confirm that certificates in the chain are valid CA |
| 23 | + certificates was overwritten. This effectively bypasses the check |
| 24 | + that non-CA certificates must not be able to issue other certificates. |
| 25 | + |
| 26 | + If a "purpose" has been configured then there is a subsequent opportunity |
| 27 | + for checks that the certificate is a valid CA. All of the named "purpose" |
| 28 | + values implemented in libcrypto perform this check. Therefore, where |
| 29 | + a purpose is set the certificate chain will still be rejected even when the |
| 30 | + strict flag has been used. A purpose is set by default in libssl client and |
| 31 | + server certificate verification routines, but it can be overridden or |
| 32 | + removed by an application. |
| 33 | + |
| 34 | + In order to be affected, an application must explicitly set the |
| 35 | + X509_V_FLAG_X509_STRICT verification flag and either not set a purpose |
| 36 | + for the certificate verification or, in the case of TLS client or server |
| 37 | + applications, override the default purpose. |
| 38 | + (CVE-2021-3450) |
| 39 | + [Tomáš Mráz] |
| 40 | + |
| 41 | + *) Fixed an issue where an OpenSSL TLS server may crash if sent a maliciously |
| 42 | + crafted renegotiation ClientHello message from a client. If a TLSv1.2 |
| 43 | + renegotiation ClientHello omits the signature_algorithms extension (where |
| 44 | + it was present in the initial ClientHello), but includes a |
| 45 | + signature_algorithms_cert extension then a NULL pointer dereference will |
| 46 | + result, leading to a crash and a denial of service attack. |
| 47 | + |
| 48 | + A server is only vulnerable if it has TLSv1.2 and renegotiation enabled |
| 49 | + (which is the default configuration). OpenSSL TLS clients are not impacted |
| 50 | + by this issue. |
| 51 | + (CVE-2021-3449) |
| 52 | + [Peter Kästle and Samuel Sapalski] |
| 53 | + |
10 | 54 | Changes between 1.1.1i and 1.1.1j [16 Feb 2021]
|
11 | 55 |
|
12 | 56 | *) Fixed the X509_issuer_and_serial_hash() function. It attempts to
|
|
0 commit comments