cve.bz

CVE-2022-1434

5.9 mediumEPSS 1.2%Fix available

Medium (5.9). EPSS 1.2% estimated probability of exploitation activity in the next 30 days. Fixed in openssl-src 300.0.6.

On this page
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).

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
1.2% (unchanged from 1.2% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 69th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-1434 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-1434?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-1434?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-1434 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2022-1434

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2022-1434](https://cve.bz/cve/badge/CVE-2022-1434.svg)](https://cve.bz/cve/CVE-2022-1434)

HTML:

<a href="https://cve.bz/cve/CVE-2022-1434"><img src="https://cve.bz/cve/badge/CVE-2022-1434.svg" alt="CVE-2022-1434"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openssl:opensslfrom 3.0.0 before 3.0.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-638m-m8mh-7gw2crates.ioopenssl-src>=300.0.0 <300.0.6300.0.6
RUSTSEC-2022-0026crates.ioopenssl-src>=300.0.0 <300.0.6300.0.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu18.04:LTSopenssl1.1.1-1ubuntu2.1~18.04.17USN-5402-1
Ubuntu18.04:LTSopenssl1.01.0.2n-1ubuntu5.9USN-5402-1
Ubuntu20.04:LTSopenssl1.1.1f-1ubuntu2.13USN-5402-1
Ubuntu22.04:LTSopenssl3.0.2-0ubuntu1.1UBUNTU-CVE-2022-1434 USN-5402-1
UbuntuPro:16.04:LTSedk2no fix listedUBUNTU-CVE-2022-1434
SUSELinux Enterprise Module for Basesystem 15 SP4openssl-33.0.1-150400.4.7.1SUSE-SU-2022:2306-1
openSUSELeap 15.4openssl-33.0.1-150400.4.7.1SUSE-SU-2022:2306-1
openSUSETumbleweedopenssl-33.0.5-1.1openSUSE-SU-2024:12204-1
Alpinev3.15, v3.16openssl33.0.3-r0ALPINE-CVE-2022-1434
Alpinev3.17, v3.18, v3.19 and 5 moreopenssl3.0.3-r0ALPINE-CVE-2022-1434

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw does not affect openssl as shipped in Red Hat Enterprise Linux because the vulnerable code is not built and shipped.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6opensslNot affected
Red Hat Enterprise Linux 7opensslNot affected
Red Hat Enterprise Linux 7ovmfNot affected
Red Hat Enterprise Linux 8compat-openssl10Not affected
Red Hat Enterprise Linux 8edk2Not affected
Red Hat Enterprise Linux 8opensslNot affected
Red Hat Enterprise Linux 8shimNot affected
Red Hat Enterprise Linux 9compat-openssl11Not affected
Red Hat Enterprise Linux 9edk2Not affected
Red Hat Enterprise Linux 9opensslNot affected
Red Hat Enterprise Linux 9shimNot affected
Red Hat JBoss Core Servicesjbcs-httpd24-opensslNot affected
Red Hat JBoss Web Server 3opensslNot affected
Red Hat OpenShift Container Platform 4opensslNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-1434.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-23-348-10Siemens SIMATIC S7-15002023-12-12Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and FacilitiesSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0), SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0), SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) and 2 morenone listed
ICSA-23-166-11Siemens SIMATIC S7-1500 TM MFP Linux Kernel2023-06-13MultipleSIMATIC S7-1500 TM MFP - GNU/Linux subsystemnone listed
ICSA-23-047-03Siemens Brownfield Connectivity Client2023-02-14MultipleBrownfield Connectivity - Clientnone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-97 Cryptanalysis Likelihood: Low · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-473 Signature Spoof
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-608 Cryptanalysis of Cellular Encryption Severity: High
  • CAPEC-614 Rooting SIM Cards Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON