CVE-2022-1343: OCSP_basic_verify may incorrectly verify the response signing certificate
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.1% (FIRST EPSS); higher than 81.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: openssl (AlmaLinux:9) 1:3.0.1-41.el9_0; openssl-devel (AlmaLinux:9) 1:3.0.1-41.el9_0; openssl-libs (AlmaLinux:9) 1:3.0.1-41.el9_0.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to openssl (AlmaLinux:9) 1:3.0.1-41.el9_0; openssl-devel (AlmaLinux:9) 1:3.0.1-41.el9_0; openssl-libs (AlmaLinux:9) 1:3.0.1-41.el9_0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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).
- Published
- May 3, 2022
- Updated
- Oct 14, 2026
- EPSS
- 2.1% · 81th percentile
- CWE
- CWE-295
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.3
- CNA · openssl
- 5.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
| netapp | active iq unified manager | cpe:2.3:a:netapp:active_iq_unified_manager |
| netapp | clustered data ontap | cpe:2.3:a:netapp:clustered_data_ontap |
| netapp | clustered data ontap antivirus connector | cpe:2.3:a:netapp:clustered_data_ontap_antivirus_connector |
| netapp | santricity smi-s provider | cpe:2.3:a:netapp:santricity_smi-s_provider |
| netapp | smi-s provider | cpe:2.3:a:netapp:smi-s_provider |
| netapp | snapmanager | cpe:2.3:a:netapp:snapmanager |
| netapp | solidfire, enterprise sds & hci storage node | cpe:2.3:a:netapp:solidfire,_enterprise_sds_&_hci_storage_node |
| netapp | solidfire & hci management node | cpe:2.3:a:netapp:solidfire_&_hci_management_node |
| netapp | a250 firmware | cpe:2.3:o:netapp:a250_firmware |
| netapp | a250 | cpe:2.3:h:netapp:a250 |
| netapp | a700s firmware | cpe:2.3:o:netapp:a700s_firmware |
and 31 more
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netapp a250 firmwareall versions
- netapp a700s firmwareall versions
- netapp active iq unified managerall versions
- netapp aff 500f firmwareall versions
- netapp aff 8300 firmwareall versions
- netapp aff 8700 firmwareall versions
- netapp aff a400 firmwareall versions
- netapp clustered data ontapall versions
- netapp clustered data ontap antivirus connectorall versions
- netapp fabric-attached storage a400 firmwareall versions
- netapp fas 500f firmwareall versions
- netapp fas 8300 firmwareall versions
- netapp fas 8700 firmwareall versions
- netapp h300e firmwareall versions
- netapp h300s firmwareall versions
- netapp h410s firmwareall versions
- netapp h500e firmwareall versions
- netapp h500s firmwareall versions
- netapp h700e firmwareall versions
- netapp h700s firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2)affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | openssl | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| AlmaLinux:9 | openssl-devel | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| AlmaLinux:9 | openssl-libs | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| AlmaLinux:9 | openssl-perl | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| Alpine:v3.15 | openssl3 | before 3.0.3-r0 | 3.0.3-r0 |
| Alpine:v3.17 | openssl | from 3.0.0 · before 3.0.3-r0 | 3.0.3-r0 |
| crates.io | openssl-src | from 300.0.0 · before 300.0.6 | 300.0.6 |
| openSUSE:Leap 15.4 | openssl-3 | before 3.0.1-150400.4.7.1 | 3.0.1-150400.4.7.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.0.5-1.1 | 3.0.5-1.1 |
| Red Hat:enterprise_linux:9::appstream | openssl-debuginfo | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| Red Hat:enterprise_linux:9::appstream | openssl-debugsource | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| Red Hat:enterprise_linux:9::appstream | openssl-devel | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| Red Hat:enterprise_linux:9::appstream | openssl-libs-debuginfo | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| Red Hat:enterprise_linux:9::appstream | openssl-perl | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| Red Hat:enterprise_linux:9::baseos | openssl | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| Red Hat:enterprise_linux:9::baseos | openssl-libs | before 1:3.0.1-41.el9_0 | 1:3.0.1-41.el9_0 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP4 | openssl-3 | before 3.0.1-150400.4.7.1 | 3.0.1-150400.4.7.1 |
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code 65This week
Published before and after this one in the same product
- ← EarlierCVE-2021-4160Jan 28, 2022 · BN_mod_exp may produce incorrect results on MIPS24Monitor
- ← EarlierCVE-2022-0778Mar 15, 2022 · Infinite loop in BN_mod_sqrt() reachable when parsing certificates52Plan
- Later →CVE-2022-1434May 3, 2022 · Incorrect MAC key used in the RC4-MD5 ciphersuite23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:openssl | 1:3.0.1-41.el9_0 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-devel | 1:3.0.1-41.el9_0 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-libs | 1:3.0.1-41.el9_0 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:openssl-perl | 1:3.0.1-41.el9_0 · AlmaLinux:9 | Package registry (OSV) |
| alpine:openssl | 3.0.3-r0 · Alpine:v3.17 | Package registry (OSV) |
| alpine:openssl3 | 3.0.3-r0 · Alpine:v3.15 | Package registry (OSV) |
| crates.io:openssl-src | 300.0.6 | Package registry (OSV) |
| opensuse:openssl-3 | 3.0.1-150400.4.7.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:openssl | 1:3.0.1-41.el9_0 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:openssl-debuginfo | 1:3.0.1-41.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-debugsource | 1:3.0.1-41.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-devel | 1:3.0.1-41.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-libs | 1:3.0.1-41.el9_0 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:openssl-libs-debuginfo | 1:3.0.1-41.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:openssl-perl | 1:3.0.1-41.el9_0 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| suse:openssl-3 | 3.0.1-150400.4.7.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0574 · Aug 31, 2022(RedHat Güvenlik Güncellemesi)
- TR-22-0436 · Jun 20, 2022(IBM Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
// Left empty for the test environment
}Fixed
val client = OkHttpClient.Builder()
.certificatePinner(
CertificatePinner.Builder()
.add("api.sirius.example", "sha256/…")
.build()
).build()Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=2eda98790c5c2741d76d23cc1e74b0dc4f4b391a
- security.netapp.com/advisory/ntap-20220602-0009/
- www.openssl.org/news/secadv/20220503.txt
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- cert-portal.siemens.com/productcert/html/ssa-419740.html
- cert-portal.siemens.com/productcert/html/ssa-794697.html
- cert-portal.siemens.com/productcert/html/ssa-942865.html
- cert-portal.siemens.com/productcert/html/ssa-953464.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.