OpenSSL released a security advisory to address multiple vulnerabilities affecting OpenSSL versions 3.0.0, 2.2.2, and 1.0.2 where an attacker could exploit some of these vulnerabilities to obtain sensitive information.

In one issue, there is a high-rated type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.

When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications that have implemented their own functionality for retrieving CRLs over a network.

OpenSSL versions 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue, which means:

Schneider Bold
  • OpenSSL 3.0 users should upgrade to OpenSSL 3.0.8
  • OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1t
  • OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zg (premium support customers only)

In addition, there is a timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The moderate-rated vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.

For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.

OpenSSL 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue which means:

  • OpenSSL 3.0 users should upgrade to OpenSSL 3.0.8
  • OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1t
  • OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zg (premium support customers only)

A read buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer.

The read buffer overrun might result in a crash which could lead to a denial of service attack. In theory it could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext) although we are not aware of any working exploit leading to memory contents disclosure as of the time of release of this advisory.

In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects.

OpenSSL versions 3.0.0 to 3.0.7 are vulnerable to this issue which means:

  • OpenSSL 3.0 users should upgrade to OpenSSL 3.0.8.

Click here or more information on other moderate-rated OpenSSL vulnerabilities.

Pin It on Pinterest

Share This