OpenSSL 3.0.4

Changes between 3.0.3 and 3.0.4 [21 Jun 2022]

• In addition to the c_rehash shell command injection identified in
  CVE-2022-1292, further bugs where the c_rehash script does not
  properly sanitise shell metacharacters to prevent command injection have been
  fixed.

  When the CVE-2022-1292 was fixed it was not discovered that there
  are other places in the script where the file names of certificates
  being hashed were possibly passed to a command executed through the shell.

  This script is distributed by some operating systems in a manner where
  it is automatically executed. On such operating systems, an attacker
  could execute arbitrary commands with the privileges of the script.

  Use of the c_rehash script is considered obsolete and should be replaced
  by the OpenSSL rehash command line tool.
  (CVE-2022-2068)

  Daniel Fiala, Tomáš Mráz

• Case insensitive string comparison no longer uses locales. It has instead
  been directly implemented.

  Paul Dale

OpenSSL 1.1.1p

Changes between 1.1.1o and 1.1.1p [21 Jun 2022]

• In addition to the c_rehash shell command injection identified in
  CVE-2022-1292, further bugs where the c_rehash script does not
  properly sanitise shell metacharacters to prevent command injection have been
  fixed.

  When the CVE-2022-1292 was fixed it was not discovered that there
  are other places in the script where the file names of certificates
  being hashed were possibly passed to a command executed through the shell.

  This script is distributed by some operating systems in a manner where
  it is automatically executed. On such operating systems, an attacker
  could execute arbitrary commands with the privileges of the script.

  Use of the c_rehash script is considered obsolete and should be replaced
  by the OpenSSL rehash command line tool.
  (CVE-2022-2068)
  [Daniel Fiala, Tomáš Mráz]

• When OpenSSL TLS client is connecting without any supported elliptic
  curves and TLS-1.3 protocol is disabled the connection will no longer fail
  if a ciphersuite that does not use a key exchange based on elliptic
  curves can be negotiated.
  [Tomáš Mráz]

OpenSSL 3.0.3

Changes between 3.0.2 and 3.0.3

Fixed a bug in the c_rehash script which was not properly sanitising shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script.

Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. (CVE-2022-1292)

Tomáš Mráz

Fixed a bug in the function OCSP_basic_verify that verifies the signer certificate on an OCSP response. The bug caused the function in the case where the (non-default) flag OCSP_NOCHECKS is used to return a postivie response (meaning a successful verification) even in the case where the response signing certificate fails to verify.

It is anticipated that most users of OCSP_basic_verify will not use the OCSP_NOCHECKS flag. In this case the OCSP_basic_verify function will return a negative value (indicating a fatal error) in the case of a certificate verification failure. The normal expected return value in this case would be 0.

This issue also impacts the command line OpenSSL "ocsp" application. When verifying an ocsp response with the "-no_cert_checks" option the command line application will report that the verification is successful even though it has in fact failed. In this case the incorrect successful response will also be accompanied by error messages showing the failure and contradicting the apparently successful result. ([CVE-2022-1343])

Matt Caswell

Fixed a bug where the RC4-MD5 ciphersuite incorrectly used the AAD data as the MAC key. This made the MAC key trivially predictable.

An attacker could exploit this issue by performing a man-in-the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the modified data would still pass the MAC integrity check.

Note that data sent from an OpenSSL 3.0 endpoint to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at that point. Many application protocols require data to be sent from the client to the server first. Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0 client.

If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both directions. In this case both clients and servers could be affected, regardless of the application protocol.

Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this ciphersuite.

The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt data that has been encrypted using this ciphersuite - they can only modify it.

In order for this attack to work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0 endpoint to use this ciphersuite the following must have occurred:

• OpenSSL must have been compiled with the (non-default) compile time option enable-weak-ssl-ciphers
• OpenSSL must have had the legacy provider explicitly loaded (either through application code or via configuration)
• The ciphersuite must have been explicitly added to the ciphersuite list
• The libssl security level must have been set to 0 (default is 1)
• A version of SSL/TLS below TLSv1.3 must have been negotiated
• Both endpoints must negotiate the RC4-MD5 ciphersuite in preference to any others that both endpoints have in common (CVE-2022-1434)

Matt Caswell

Fix a bug in the OPENSSL_LH_flush() function that breaks reuse of the memory occuppied by the removed hash table entries.

This function is used when decoding certificates or keys. If a long lived process periodically decodes certificates or keys its memory usage will expand without bounds and the process might be terminated by the operating system causing a denial of service. Also traversing the empty hash table entries will take increasingly more time.

Typically such long lived processes might be TLS clients or TLS servers configured to accept client certificate authentication. (CVE-2022-1473)

Hugo Landau, Aliaksei Levin

The functions OPENSSL_LH_stats and OPENSSL_LH_stats_bio now only report the num_items, num_nodes and num_alloc_nodes statistics. All other statistics are no longer supported. For compatibility, these statistics are still listed in the output but are now always reported as zero.

Hugo Landau

OpenSSL 1.1.1o

Changes between 1.1.1n and 1.1.1o [3 May 2022]

Fixed a bug in the c_rehash script which was not properly sanitising shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed.
On such operating systems, an attacker could execute arbitrary commands with the privileges of the script.

Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. (CVE-2022-1292)
[Tomáš Mráz]

OpenSSL 3.0.2

Changes between 3.0.1 and 3.0.2 [15 mar 2022]

Fixed a bug in the BN_mod_sqrt() function that can cause it to loop forever for non-prime moduli.

Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form.

It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters.

Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters.

Thus vulnerable situations include:

• TLS clients consuming server certificates
• TLS servers consuming client certificates
• Hosting providers taking certificates or private keys from customers
• Certificate authorities parsing certification requests from subscribers
• Anything else which parses ASN.1 elliptic curve parameters
• Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. ([CVE-2022-0778])

Tomáš Mráz

Add ciphersuites based on DHE_PSK (RFC 4279) and ECDHE_PSK (RFC 5489) to the list of ciphersuites providing Perfect Forward Secrecy as required by SECLEVEL >= 3.

Dmitry Belyavskiy, Nicola Tuveri

Made the AES constant time code for no-asm configurations optional due to the resulting 95% performance degradation. The AES constant time code can be enabled, for no assembly builds, with: ./config no-asm -DOPENSSL_AES_CONST_TIME

Paul Dale

Fixed PEM_write_bio_PKCS8PrivateKey() to make it possible to use empty passphrase strings.

Darshan Sen

The negative return value handling of the certificate verification callback was reverted. The replacement is to set the verification retry state with the SSL_set_retry_verify() function.

Tomáš Mráz

OpenSSL 1.1.1n

Changes between 1.1.1m and 1.1.1n [15 Mar 2022]

Fixed a bug in the BN_mod_sqrt() function that can cause it to loop forever for non-prime moduli.

Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form.

It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters.

Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters.

Thus vulnerable situations include:

  - TLS clients consuming server certificates
  - TLS servers consuming client certificates
  - Hosting providers taking certificates or private keys from customers
  - Certificate authorities parsing certification requests from subscribers
  - Anything else which parses ASN.1 elliptic curve parameters

Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. (CVE-2022-0778) [Tomáš Mráz]

Add ciphersuites based on DHE_PSK (RFC 4279) and ECDHE_PSK (RFC 5489) to the list of ciphersuites providing Perfect Forward Secrecy as required by SECLEVEL >= 3. [Dmitry Belyavskiy, Nicola Tuveri]

OpenSSL 3.0.1

Changes between 3.0.0 and 3.0.1 [14 dec 2021]

• Fixed invalid handling of X509_verify_cert() internal errors in libssl Internally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error() to return the value SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be returned by OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Since most applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be totally unexpected and applications may not behave correctly as a result. The exact behaviour will depend on the application but it could result in crashes, infinite loops or other similar incorrect responses.

This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause X509_verify_cert() to indicate an internal error when processing a certificate chain. This will occur where a certificate does not include the Subject Alternative Name extension but where a Certificate Authority has enforced name constraints. This issue can occur even with valid chains. ([CVE-2021-4044])

• Corrected a few file name and file reference bugs in the build, installation and setup scripts, which lead to installation verification failures. Slightly enhanced the installation verification script.
• Fixed EVP_PKEY_eq() to make it possible to use it with strictly private keys.
• Fixed PVK encoder to properly query for the passphrase.
• Multiple fixes in the OSSL_HTTP API functions.
• Allow sign extension in OSSL_PARAM_allocate_from_text() for the OSSL_PARAM_INTEGER data type and return error on negative numbers used with the OSSL_PARAM_UNSIGNED_INTEGER data type. Make OSSL_PARAM_BLD_push_BN{,_pad}() return an error on negative numbers.
• Allow copying uninitialized digest contexts with EVP_MD_CTX_copy_ex.
• Fixed detection of ARMv7 and ARM64 CPU features on FreeBSD.
• Multiple threading fixes.
• Added NULL digest implementation to keep compatibility with 1.1.1 version.
• Allow fetching an operation from the provider that owns an unexportable key as a fallback if that is still allowed by the property query.

OpenSSL 1.1.1m

Changes between 1.1.1l and 1.1.1m [14 Dec 2021]

• Avoid loading of a dynamic engine twice
• Fixed building on Debian with kfreebsd kernels
• Prioritise DANE TLSA issuer certs over peer certs
• Fixed random API for MacOS prior to 10.12

OpenSSL 3.0.0

OpenSSL 3.0

OpenSSL 1.1.1l

Major changes between OpenSSL 1.1.1k and OpenSSL 1.1.1l [24 Aug 2021]

• Fixed an SM2 Decryption Buffer Overflow (CVE-2021-3711)
• Fixed various read buffer overruns processing ASN.1 strings (CVE-2021-3712)