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 whe…
Exact source revision recorded 24 Oct 2026 19:17:43 UTC. It does not establish the source's current position. Latest evidence.
nvd · CVE-2022-1343
PublishedThe 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).
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-295
Original publisher date fields
published: 2022-05-03T16:15:18.873
lastModified: 2026-10-14T13:17:18.587
43 source CPE criteria · context only
- cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*
- cpe:2.3:a:netapp:active_iq_unified_manager:-:*:*:*:*:vsphere:*:*
- cpe:2.3:a:netapp:clustered_data_ontap:-:*:*:*:*:*:*:*
- cpe:2.3:a:netapp:clustered_data_ontap_antivirus_connector:-:*:*:*:*:*:*:*
- cpe:2.3:a:netapp:santricity_smi-s_provider:-:*:*:*:*:*:*:*
- cpe:2.3:a:netapp:smi-s_provider:-:*:*:*:*:*:*:*
- cpe:2.3:a:netapp:snapmanager:-:*:*:*:*:hyper-v:*:*
- cpe:2.3:a:netapp:solidfire\,_enterprise_sds_\&_hci_storage_node:-:*:*:*:*:*:*:*
- cpe:2.3:a:netapp:solidfire_\&_hci_management_node:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:a250_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:a250:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:a700s_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:a700s:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:aff_500f_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:aff_500f:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:aff_8300_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:aff_8300:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:aff_8700_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:aff_8700:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:aff_a400_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:aff_a400:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:fabric-attached_storage_a400_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:fabric-attached_storage_a400:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:fas_500f_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:fas_500f:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:fas_8300_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:fas_8300:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:fas_8700_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:fas_8700:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:h300e_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:h300e:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:h300s_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:h300s:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:h410s_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:h410s:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:h500e_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:h500e:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:h500s_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:h500s:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:h700e_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:h700e:-:*:*:*:*:*:*:*
- cpe:2.3:o:netapp:h700s_firmware:-:*:*:*:*:*:*:*
- cpe:2.3:h:netapp:h700s:-:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 3 May 2022 16:15:18 UTC
- Source modified
- 14 Oct 2026 13:17:18 UTC
- Observed here
- 24 Oct 2026 19:17:43 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS 3.1 · [email protected] · Primary · 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary · 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CVSS 2.0 · [email protected] · Primary · 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N