ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2022-1434

The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key.

Published May 3, 2022 · catalog updated Oct 14, 2026 · The OpenSSL 3.0 implementation

Check if you run it

No confirmed exploitation is on record for CVE-2022-1434. EPSS is 1.20%. Act only if a listed version of The OpenSSL 3.0 implementation is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The OpenSSL 3.0 implementation).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.20%
Remediation
Advisory link
Affected products
cpe netapp/a700s firmware · cpe netapp/active iq unified manager · cpe netapp/clustered data ontap · cpe netapp/clustered data ontap antivirus connector · cpe netapp/h300s firmware · cpe netapp/h500s firmware

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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe netapp/a700s firmwareversion unspecified
  • cpe netapp/active iq unified managerversion unspecified
  • cpe netapp/clustered data ontapversion unspecified
  • cpe netapp/clustered data ontap antivirus connectorversion unspecified
  • cpe netapp/h300s firmwareversion unspecified
  • cpe netapp/h500s firmwareversion unspecified
  • cpe netapp/h700s firmwareversion unspecified
  • cpe netapp/santricity smi-s providerversion unspecified
  • cpe netapp/smi-s providerversion unspecified
  • cpe netapp/snapmanagerversion unspecified
  • cpe netapp/solidfire, enterprise sds & hci storage nodeversion unspecified
  • cpe openssl/opensslversion unspecified

How to fix CVE-2022-1434

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2022-1434. EPSS is 1.20%. Act only if a listed version of The OpenSSL 3.0 implementation is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-327: Use of a Broken or Risky Cryptographic Algorithm. EPSS 1.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 3, 2022 · NIST NVD

    Detected

    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 Op

  2. Oct 14, 2026 · NIST NVD

    Updated

    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 Op

Sources

  • CVE.orgVulnerability recordCVE-2022-1434

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2022-1434

    30-day exploitation probability 1.2%

    first.org
  • NIST NVDVulnerability recordCVE-2022-1434

    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 Op

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.