This vulnerability is marked as RESERVED by NVD. This means that the CVE-ID is reserved for future use by the CVE Numbering Authority (CNA) or a security researcher, but the details of it are not yet publicly available yet.
This page will reflect the classification results once they are available through NVD.
Any vendor information available is shown as below.
CVE-2021-3450 openssl: CA certificate check bypass with X509_V_FLAG_X509_STRICT
The following conditions have to be met for an application compiled with OpenSSL to be vulnerable:
|JBoss Core Services on RHEL 7||RedHat|
|Red Hat Enterprise Linux 8||RedHat||openssl-1:1.1.1g-15.el8_3|
|Red Hat JBoss Core Services 1||RedHat|
|Red Hat JBoss Web Server 3.1||RedHat|
|Red Hat JBoss Web Server 3 for RHEL 7||RedHat||tomcat-native-0:1.2.23-24.redhat_24.ep7.el7|
|Red Hat JBoss Web Server 5||RedHat|
|Red Hat JBoss Web Server 5.4 on RHEL 7||RedHat||jws5-tomcat-native-0:1.2.25-4.redhat_4.el7jws|
|Red Hat JBoss Web Server 5.4 on RHEL 8||RedHat||jws5-tomcat-native-0:1.2.25-4.redhat_4.el8jws|
|Red Hat Virtualization 4 for Red Hat Enterprise Linux 8||RedHat||redhat-virtualization-host-0:4.4.5-20210330.0.el8_3|
The X509_V_FLAG_X509_STRICT 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. OpenSSL versions 1.1.1h and newer are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1h-1.1.1j).
|Openssl||Ubuntu/trusty||out of standard support|
|Edk2||Ubuntu/trusty||out of standard support|
|Nodejs||Ubuntu/trusty||out of standard support|