CVE-2022-1434: Incorrect MAC key used in the RC4-MD5 ciphersuite
Noroxi assessment
Priority: Monitor (action score 23/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: 1.2% (FIRST EPSS); higher than 68.7% 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. Special conditions such as timing or configuration are required.
- Fixed version: openssl3 (Alpine:v3.15) 3.0.3-r0; openssl (Alpine:v3.17) 3.0.3-r0; openssl-src (crates.io) 300.0.6.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to openssl3 (Alpine:v3.15) 3.0.3-r0; openssl (Alpine:v3.17) 3.0.3-r0; openssl-src (crates.io) 300.0.6 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 OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key. This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at that point. Many application protocols require data to be sent from the client to the server first. Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0 client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both directions. In this case both clients and servers could be affected, regardless of the application protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0 endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is 1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the RC4-MD5 ciphersuite in preference to any others that both endpoints have in common 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
- 1.2% · 68th percentile
- CWE
- CWE-327
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
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 | a700s firmware | cpe:2.3:o:netapp:a700s_firmware |
| netapp | a700s | cpe:2.3:h:netapp:a700s |
| netapp | h300s firmware | cpe:2.3:o:netapp:h300s_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 |
|---|---|---|---|
| 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 |
| 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-2022-0778Mar 15, 2022 · Infinite loop in BN_mod_sqrt() reachable when parsing certificates52Plan
- ← EarlierCVE-2022-1343May 3, 2022 · OCSP_basic_verify may incorrectly verify the response signing certificate22Monitor
- Later →CVE-2022-1473May 3, 2022 · Resource leakage when decoding certificates and keys31Monitor
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 |
|---|---|---|
| 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) |
| 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.
No history yet (it accumulates with the daily EPSS job).
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-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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-327 · Use of a Broken or Risky Cryptographic AlgorithmCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
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)
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Signature SpoofCAPEC-473
- Signature Spoofing by Improper ValidationCAPEC-475likelihood: Low · High
- Cryptanalysis of Cellular EncryptionCAPEC-608High
- Rooting SIM CardsCAPEC-614High
- CryptanalysisCAPEC-97likelihood: Low · Very High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=7d56a74a96828985db7354a55227a511615f732b
- 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-794697.html
- cert-portal.siemens.com/productcert/html/ssa-953464.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.