Описание
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 verif...
Релиз | Статус | Примечание |
---|---|---|
bionic | not-affected | |
devel | not-affected | |
esm-apps/bionic | not-affected | |
esm-apps/xenial | not-affected | |
esm-infra-legacy/trusty | DNE | |
esm-infra/focal | not-affected | |
focal | not-affected | |
groovy | not-affected | |
precise/esm | DNE | |
trusty | ignored | end of standard support |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | not-affected | uses system openssl1.0 |
devel | not-affected | uses system openssl1.1 |
esm-apps/bionic | not-affected | uses system openssl1.0 |
esm-apps/focal | not-affected | uses system openssl1.1 |
esm-apps/xenial | not-affected | uses system openssl |
esm-infra-legacy/trusty | not-affected | uses system openssl |
focal | not-affected | uses system openssl1.1 |
groovy | not-affected | uses system openssl1.1 |
precise/esm | DNE | |
trusty | ignored | end of standard support |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | not-affected | 1.1.1-1ubuntu2.1~18.04.8 |
devel | released | 1.1.1j-1ubuntu3 |
esm-infra-legacy/trusty | not-affected | |
esm-infra/bionic | not-affected | 1.1.1-1ubuntu2.1~18.04.8 |
esm-infra/focal | not-affected | 1.1.1f-1ubuntu2.2 |
esm-infra/xenial | not-affected | 1.0.2g-1ubuntu4.19 |
focal | not-affected | 1.1.1f-1ubuntu2.2 |
groovy | not-affected | 1.1.1f-1ubuntu4.2 |
precise/esm | not-affected | |
trusty | ignored | end of standard support |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | not-affected | 1.0.2n-1ubuntu5.6 |
devel | DNE | |
esm-infra-legacy/trusty | DNE | |
esm-infra/bionic | not-affected | 1.0.2n-1ubuntu5.6 |
esm-infra/focal | DNE | |
focal | DNE | |
groovy | DNE | |
precise/esm | DNE | |
trusty | DNE | |
trusty/esm | DNE |
Показывать по
EPSS
5.8 Medium
CVSS2
7.4 High
CVSS3
Связанные уязвимости
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 verif...
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 verifica
OpenSSL: CVE-2021-3450 CA certificate check bypass with X509_V_FLAG_X509_STRICT
The X509_V_FLAG_X509_STRICT flag enables additional security checks of ...
EPSS
5.8 Medium
CVSS2
7.4 High
CVSS3