CVE-2022-1434 — Incorrect MAC key used in the RC4-MD5 ciphersuite
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).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 1.1% (30-day exploitation probability)+10
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Rust Openssl-src: fixed in version 300.0.6 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Netapp A250 Firmware, Netapp A700s Firmware, Netapp Active Iq Unified Manager…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Netapp | A250 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | A700s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Active Iq Unified Manager | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Aff 500f Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Aff 8300 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Aff 8700 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Aff A400 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Clustered Data Ontap | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Clustered Data Ontap Antivirus Connector | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Fabric-attached Storage A400 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Fas 500f Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Fas 8300 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Fas 8700 Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H300e Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H300s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H410s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H500e Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H500s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H700e Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H700s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Santricity Smi-s Provider | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Smi-s Provider | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Snapmanager | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Solidfire & Hci Management Node | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Solidfire, Enterprise Sds & Hci Storage Node | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Openssl | Openssl | version Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2) | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Openssl | Openssl | ≥ 3.0.0 and < 3.0.3 | Vulnerable | NIST National Vulnerability Database |
| Rust | Openssl-src | ≥ 300.0.0 and < 300.0.6 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.9 | CVSS 3.1 | Medium | 2.2 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.9 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 4.3 | CVSS 2.0 | Medium | 8.6 | 2.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.06%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Check TLS negotiations and unexpected certificates in the component’s traffic.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · rust/openssl-src
- Affected products added · openssl/openssl
- Record published
- Affected products added · openssl/openssl, netapp/active iq unified manager, netapp/clustered data ontap, netapp/clustered data ontap antivirus co
- CVSS changed · 5.9
- Source status changed · → Modified
- Record created in this database
- 2022
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
12 on the record
- www.openssl.org/news/secadv/20220503.txt
- nvd.nist.gov/vuln/detail/CVE-2022-1434
- github.com/advisories/GHSA-638m-m8mh-7gw2
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- git.openssl.org/gitweb/
- cert-portal.siemens.com/productcert/html/ssa-953464.html
- rustsec.org/advisories/RUSTSEC-2022-0026.html
- git.openssl.org/gitweb/
- cert-portal.siemens.com/productcert/html/ssa-794697.html
- cert-portal.siemens.com/productcert/pdf/ssa-953464.pdf
- github.com/github/advisory-database/issues/405
- security.netapp.com/advisory/ntap-20220602-0009/
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-84784 QUIC: Unbounded RETIRE_CONNECTION_ID Backlog 16d
- High CVE-2026-84782 DTLS Retransmits Handshake Messages From a Stale Buffer Offset 16d
- High CVE-2026-84783 Use-After-Free in X.509 Extension Cache Under Concurrent Use 16d
- Low CVE-2026-77696 Timing Side-Channel in SM2 Signature Generation 16d
- Medium CVE-2026-75806 Unauthenticated and Undersized DTLS 1.2 AEAD Record Causes DoS 16d
- Medium CVE-2026-75805 NULL Pointer Dereference in CMP Client Revocation Response Handling 16d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-1434 is "Incorrect MAC key used in the RC4-MD5 ciphersuite", rated Medium. It affects A250 Firmware (Netapp); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.9 describes technical severity. EPSS 1.06% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.