How severe is CVE-2022-1343?

CVE-2022-1343 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-1343?

CVE-2022-1343 affects the following packages: openssl-src (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2022-1343?

Update openssl-src to 300.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1343 is resolved across your whole dependency graph.

How do I detect CVE-2022-1343 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl-src, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-1343 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-1343 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-1343 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-1343?

CVE-2022-1343 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-1343?

CVE-2022-1343 is classified as CWE-295 (CWE-295). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-1343 published, and has it been updated?

CVE-2022-1343 was published on May 3, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

MEDIUM severity

CVE-2022-1343 — openssl-src

MEDIUM

CVE-2022-1343 is a medium-severity (CVSS 5.3) CWE-295 vulnerability in openssl-src. A fix is available for openssl-src — see the affected versions and patch details below.

OCSP_basic_verify may incorrectly verify the response signing certificate

Also known asGHSA-mfm6-r9g2-q4r7RUSTSEC-2022-0027

Published

May 3, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-1343.

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🦀openssl-src

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`openssl-src`	≥ 300.0.0&&< 300.0.6	300.0.6`cargo update -p openssl-src --precise 300.0.6`

Affected Products

26 products · 26 configurations

a250 firmwarenetapp

all

a700s firmwarenetapp

all

Application

active iq unified managernetapp

all

aff 500f firmwarenetapp

all

aff 8300 firmwarenetapp

all

aff 8700 firmwarenetapp

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl-src, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openssl-src to 300.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1343 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This flaw impact has been rated Moderate because the configuration required for it to occur is non-default, not common, and there is still an indication of failure at the CLI for the OCSP application.

Product	Fixed in	Advisory
Red Hat Enterprise Linux 9	`openssl-1:3.0.1-41.el9_0`	RHSA-2022:6224

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2022-1343 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works