The function OCSP_basic_verify verifies the signer certificate on an OCSP response. In the case where the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (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. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).
The product does not validate, or incorrectly validates, a certificate.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Openssl | Openssl | 3.0.0 (including) | 3.0.3 (excluding) |
| Red Hat Enterprise Linux 9 | RedHat | openssl-1:3.0.1-41.el9_0 | * |
| Red Hat Enterprise Linux 9 | RedHat | openssl-1:3.0.1-41.el9_0 | * |
| Edk2 | Ubuntu | trusty | * |
| Edk2 | Ubuntu | upstream | * |
| Edk2 | Ubuntu | xenial | * |
| Nodejs | Ubuntu | trusty | * |
| Openssl | Ubuntu | devel | * |
| Openssl | Ubuntu | fips-preview/jammy | * |
| Openssl | Ubuntu | fips-updates/jammy | * |
| Openssl | Ubuntu | jammy | * |
| Openssl | Ubuntu | kinetic | * |
| Openssl | Ubuntu | lunar | * |
| Openssl | Ubuntu | mantic | * |
| Openssl | Ubuntu | noble | * |
| Openssl | Ubuntu | upstream | * |