OpenSSLFramework / library
CVE-2022-1343
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe OCSP_basic_verify function in OpenSSL 3.0.0-3.0.2 incorrectly returns a positive verification result when the OCSP_NOCHECKS flag is set, even when the response signing certificate fails to verify. Without this flag, the function returns a negative value (fatal error) instead of the expected 0 (verification failure). The command-line 'ocsp' application exhibits the same flaw when using the '-no_cert_checks' option, reporting success despite underlying certificate verification failures.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OpenSSLFramework / library
>= 3.0.0, < 3.0.3all versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check OpenSSL versionRun 'openssl version' or check the library file version to determine if it is 3.0.0, 3.0.1, or 3.0.2Affected if The installed version is 3.0.0, 3.0.1, or 3.0.2 (versions before 3.0.3)
-
Identify OCSP_NOCHECKS usage in application codeSearch source code for uses of the OCSP_NOCHECKS flag in calls to OCSP_basic_verify or similar OCSP verification functionsAffected if The OCSP_NOCHECKS flag is set in OCSP verification code in the environment
-
Check for ocsp command-line -no_cert_checks optionReview any scripts or automation that invoke 'openssl ocsp' with the '-no_cert_checks' flagAffected if The '-no_cert_checks' option is used with the openssl ocsp command
-
Verify NetApp product OpenSSL dependencyFor NetApp products listed (Active IQ Unified Manager, Clustered Data Ontap, etc.), determine the OpenSSL version bundled or used by the productAffected if The NetApp product ships with or uses a vulnerable OpenSSL 3.0.0-3.0.2 version and performs OCSP verification with the NOCHECKS flag enabled
-
Review OCSP response verification logicExamine application configuration or code paths that handle OCSP responses, looking for conditional logic that sets the NOCHECKS flag based on user input or configAffected if OCSP verification is performed with OCSP_NOCHECKS enabled, which bypasses certificate chain validation
You are affected if your OpenSSL version is 3.0.0 through 3.0.2 AND OCSP verification is performed with the OCSP_NOCHECKS flag (or -no_cert_checks CLI option) enabled, causing invalid OCSP responses to be incorrectly accepted as valid.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.0.3
Upgrade to OpenSSL 3.0.3 or later. Avoid using the OCSP_NOCHECKS flag or -no_cert_checks option in affected versions until the patch is applied.
OpenSSL 3.0.3 or later (3.0.4, 3.0.5, etc.)
- Identify the current OpenSSL version by running 'openssl version' or checking the library files
- For standalone OpenSSL installations: Download OpenSSL 3.0.3 or later from the official OpenSSL website (www.openssl.org) or your Linux distribution's package manager
- Upgrade OpenSSL: On RHEL/CentOS use 'sudo yum update openssl' or on Debian/Ubuntu use 'sudo apt update && sudo apt install openssl'
- Verify the upgrade was successful by running 'openssl version' and confirming it shows 3.0.3 or higher
- For NetApp products (Active IQ Unified Manager, Clustered Data Ontap, etc.): Check NetApp's security advisory at security.netapp.com for product-specific patches or updated versions
- Apply any vendor-specific patches or updates for the affected NetApp or other products listed in the vulnerability description
- Test OCSP verification functionality to confirm the fix works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in OpenSSL
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-1343 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data