BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-1434High confidence

Incorrect MAC key used in the RC4-MD5 ciphersuite

OpenSSL · OpenSSL

5.9MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

3 current
SSA-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < V3.1.5
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC 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)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Summary
When using the RC4-MD5 ciphersuite, which is disabled by default, an attacker is able to modify data in transit due to an incorrect use of the AAD data as the MAC key in OpenSSL 3.0. An attacker is not able to decrypt any communication.
Remediation
Update to V3.1.5 or later version
SSA-794697 · CSAF 2.0 · revision 9 · interimSiemens ProductCERTSSA-794697: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP before V1.1
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Summary
When using the RC4-MD5 ciphersuite, which is disabled by default, an attacker is able to modify data in transit due to an incorrect use of the AAD data as the MAC key in OpenSSL 3.0. An attacker is not able to decrypt any communication.
Remediation
Update to V1.1 or later version
SSA-953464 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-953464: Multiple Vulnerabilites in Siemens Brownfield Connectivity - Client before V2.15
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • Brownfield Connectivity - Client
Summary
When using the RC4-MD5 ciphersuite, which is disabled by default, an attacker is able to modify data in transit due to an incorrect use of the AAD data as the MAC key in OpenSSL 3.0. An attacker is not able to decrypt any communication.
Remediation
Update to V2.15 or later version Contact customer support to obtain the update
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-2698

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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).

What

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).

Why

The product uses a broken or risky cryptographic algorithm or protocol.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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).

Why

The product uses a broken or risky cryptographic algorithm or protocol.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Use of a Broken or Risky Cryptographic Algorithm → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-327 ↗

CWE-327: Use of a Broken or Risky Cryptographic Algorithm. The product uses a broken or risky cryptographic algorithm or protocol.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-327
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-W-2023-1432Siemens SIMATIC S7: Mehrere Schwachstellen

Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter, anonymer, authentisierter, physischer oder lokaler Angreifer kann mehrere Schwachstellen in Siemens SIMATIC S7 ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen, seine Privilegien zu erweitern und Daten zu manipulieren.

Official advisory
BSI · German · WID-SEC-W-2022-0071OpenSSL: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in OpenSSL ausnutzen, um beliebigen Programmcode mit den Rechten des Dienstes auszuführen, Sicherheitsvorkehrungen zu umgehen, Dateien zu manipulieren oder einen Denial of Service Zustand herbeizuführen.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

g/CVERecord?id=CVE-2021-43816 Référence CVE CVE-2021-44716 https://www.cve.org/CVERecord?id=CVE-2021-44716 Référence CVE CVE-2021-44717 https://www.cve.org/CVERecord?id=CVE-2021-44717 Référence CVE CVE-2021-46848 https://www.cve.org/CVERecord?id=CVE-2021-46848 Référence CVE CVE-2022-0563 https://www.cve.org/CVERecord?id=CVE-2022-0563 Référence CVE CVE-2022-0778 https://www.cve.org/CVERecord?id=CVE-2022-0778 Référence CVE CVE-2022-1271 https://www.cve.org/CVERecord?id=CVE-2022-1271 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1471 https://www.cve.org/CVERecord?id=CVE-2022-1471 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-1705 https://www.cve.org/CVERecord?id=CVE-2022-1705 Référence CVE CVE-2022-1962 https://www.cve.org/CVERecord?id=CVE-2022-1962 Référence CVE CVE-2022-2068 https://www.cve.org/CVERecord?id=CVE-2022-2068 Référence CVE CVE-2022-2097 https://www.cve.org/CVERecord?id=CVE-2022-2097 Référence CVE CVE-2022-21619 https://www.cve.org/CVERecord?id=CVE-2022-21619 Référence CVE CVE-2022-21624 https://www.cve.org/CVERecord?id=CVE-2022-2162

Official advisory
CERT-FR · French · CERTFR-2025-AVI-1054Multiples vulnérabilités dans les produits VMware

sécurité VMware 36557 du 30 novembre 2025 https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36557 Bulletin de sécurité VMware 36558 du 30 novembre 2025 https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36558 Bulletin de sécurité VMware 36559 du 30 novembre 2025 https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36559 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-2068 https://www.cve.org/CVERecord?id=CVE-2022-2068 Référence CVE CVE-2022-2097 https://www.cve.org/CVERecord?id=CVE-2022-2097 Référence CVE CVE-2022-3358 https://www.cve.org/CVERecord?id=CVE-2022-3358 Référence CVE CVE-2022-3602 https://www.cve.org/CVERecord?id=CVE-2022-3602 Référence CVE CVE-2022-3786 https://www.cve.org/CVERecord?id=CVE-2022-3786 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-4203 https://www.cve.org/CVERecord?id=CVE-2022-4203 Ré

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

.cve.org/CVERecord?id=CVE-2022-1115 Référence CVE CVE-2022-1210 https://www.cve.org/CVERecord?id=CVE-2022-1210 Référence CVE CVE-2022-1271 https://www.cve.org/CVERecord?id=CVE-2022-1271 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1304 https://www.cve.org/CVERecord?id=CVE-2022-1304 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1354 https://www.cve.org/CVERecord?id=CVE-2022-1354 Référence CVE CVE-2022-1355 https://www.cve.org/CVERecord?id=CVE-2022-1355 Référence CVE CVE-2022-1420 https://www.cve.org/CVERecord?id=CVE-2022-1420 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-1586 https://www.cve.org/CVERecord?id=CVE-2022-1586 Référence CVE CVE-2022-1587 https://www.cve.org/CVERecord?id=CVE-2022-1587 Référence CVE CVE-2022-1615 https://www.cve.org/CVERecord?id=CVE-2022-1615 Référence CVE CVE-2022-1622 https://www.cve.org/CVERecord?id=CVE-2022-1622 Référence CVE CVE-2022-1623 https://www.cve.org/CVERecord?id=CVE-2022-1623 Référence CVE CVE-2022-1674 https://www.cve.org/CVERecord?id=CVE-2022-1674 Référence CVE CVE-2022-1705 https://www.cve.org/CVERecord?id=CVE-2022-1705 Ré

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0967Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2021-35564 Référence CVE CVE-2021-35565 https://www.cve.org/CVERecord?id=CVE-2021-35565 Référence CVE CVE-2021-35567 https://www.cve.org/CVERecord?id=CVE-2021-35567 Référence CVE CVE-2021-35578 https://www.cve.org/CVERecord?id=CVE-2021-35578 Référence CVE CVE-2021-35586 https://www.cve.org/CVERecord?id=CVE-2021-35586 Référence CVE CVE-2021-35588 https://www.cve.org/CVERecord?id=CVE-2021-35588 Référence CVE CVE-2021-35603 https://www.cve.org/CVERecord?id=CVE-2021-35603 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-2068 https://www.cve.org/CVERecord?id=CVE-2022-2068 Référence CVE CVE-2022-2097 https://www.cve.org/CVERecord?id=CVE-2022-2097 Référence CVE CVE-2022-21248 https://www.cve.org/CVERecord?id=CVE-2022-21248 Référence CVE CVE-2022-21271 https://www.cve.org/CVERecord?id=CVE-2022-21271 Référence CVE CVE-2022-21282 https://www.cve.org/CVERecord?id=CVE-2022-21282 Référence CVE CVE-2022-21291 https://www.cve.org/CVERecord?id=CVE-2022-21291 Référence CVE CVE-2022-21293 https://www.cve.org/CVERecord?id=CVE-202

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0864Multiples vulnérabilités dans VMware Tanzu

rg/CVERecord?id=CVE-2013-4235 Référence CVE CVE-2016-20013 https://www.cve.org/CVERecord?id=CVE-2016-20013 Référence CVE CVE-2016-2781 https://www.cve.org/CVERecord?id=CVE-2016-2781 Référence CVE CVE-2017-11164 https://www.cve.org/CVERecord?id=CVE-2017-11164 Référence CVE CVE-2021-4189 https://www.cve.org/CVERecord?id=CVE-2021-4189 Référence CVE CVE-2021-46848 https://www.cve.org/CVERecord?id=CVE-2021-46848 Référence CVE CVE-2022-0391 https://www.cve.org/CVERecord?id=CVE-2022-0391 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-2068 https://www.cve.org/CVERecord?id=CVE-2022-2068 Référence CVE CVE-2022-2097 https://www.cve.org/CVERecord?id=CVE-2022-2097 Référence CVE CVE-2022-3358 https://www.cve.org/CVERecord?id=CVE-2022-3358 Référence CVE CVE-2022-3602 https://www.cve.org/CVERecord?id=CVE-2022-3602 Référence CVE CVE-2022-3786 https://www.cve.org/CVERecord?id=CVE-2022-3786 Référence CVE CVE-2022-3996 https://www.cve.org/CVERecord?id=CVE-2022-3996 Référence CVE CVE-2022-40735 https://www.cve.org/CVERecord?id=CVE-2022-40735

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0622Multiples vulnérabilités dans les produits VMware

e.org/CVERecord?id=CVE-2020-22916 Référence CVE CVE-2020-36843 https://www.cve.org/CVERecord?id=CVE-2020-36843 Référence CVE CVE-2020-8908 https://www.cve.org/CVERecord?id=CVE-2020-8908 Référence CVE CVE-2021-3995 https://www.cve.org/CVERecord?id=CVE-2021-3995 Référence CVE CVE-2021-3996 https://www.cve.org/CVERecord?id=CVE-2021-3996 Référence CVE CVE-2022-0563 https://www.cve.org/CVERecord?id=CVE-2022-0563 Référence CVE CVE-2022-1271 https://www.cve.org/CVERecord?id=CVE-2022-1271 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-1705 https://www.cve.org/CVERecord?id=CVE-2022-1705 Référence CVE CVE-2022-1962 https://www.cve.org/CVERecord?id=CVE-2022-1962 Référence CVE CVE-2022-2068 https://www.cve.org/CVERecord?id=CVE-2022-2068 Référence CVE CVE-2022-2097 https://www.cve.org/CVERecord?id=CVE-2022-2097 Référence CVE CVE-2022-21698 https://www.cve.org/CVERecord?id=CVE-2022-21698 Référence CVE CVE-2022-22576 https://www.cve.org/CVERecord?id=CVE-2022-22576 Référence CVE CVE-2022-23471 https://www.cve.org/CVERecord?id=CVE-2022-23

Official advisory
CERT-FR · French · CERTFR-2023-AVI-1015Multiples vulnérabilités dans les produits Siemens

e.org/CVERecord?id=CVE-2021-46828 Référence CVE CVE-2021-46848 https://www.cve.org/CVERecord?id=CVE-2021-46848 Référence CVE CVE-2022-0391 https://www.cve.org/CVERecord?id=CVE-2022-0391 Référence CVE CVE-2022-0563 https://www.cve.org/CVERecord?id=CVE-2022-0563 Référence CVE CVE-2022-0778 https://www.cve.org/CVERecord?id=CVE-2022-0778 Référence CVE CVE-2022-1271 https://www.cve.org/CVERecord?id=CVE-2022-1271 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1304 https://www.cve.org/CVERecord?id=CVE-2022-1304 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-2068 https://www.cve.org/CVERecord?id=CVE-2022-2068 Référence CVE CVE-2022-2097 https://www.cve.org/CVERecord?id=CVE-2022-2097 Référence CVE CVE-2022-22576 https://www.cve.org/CVERecord?id=CVE-2022-22576 Référence CVE CVE-2022-2274 https://www.cve.org/CVERecord?id=CVE-2022-2274 Référence CVE CVE-2022-22822 https://www.cve.org/CVERecord?id=CVE-2022-22822 Référence CVE CVE-2022-22823 https://www.cve.org/CVERecord?id=CVE-2022-22823 Référence CVE CVE-2022-22824 https://www.cve.org/CVERecord?id=CVE-2022-

Official advisory
CERT-FR · French · CERTFR-2023-AVI-0453Multiples vulnérabilités dans les produits Siemens

e.org/CVERecord?id=CVE-2021-42385 Référence CVE CVE-2021-42386 https://www.cve.org/CVERecord?id=CVE-2021-42386 Référence CVE CVE-2022-0171 https://www.cve.org/CVERecord?id=CVE-2022-0171 Référence CVE CVE-2022-0547 https://www.cve.org/CVERecord?id=CVE-2022-0547 Référence CVE CVE-2022-1012 https://www.cve.org/CVERecord?id=CVE-2022-1012 Référence CVE CVE-2022-1184 https://www.cve.org/CVERecord?id=CVE-2022-1184 Référence CVE CVE-2022-1199 https://www.cve.org/CVERecord?id=CVE-2022-1199 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1462 https://www.cve.org/CVERecord?id=CVE-2022-1462 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-1679 https://www.cve.org/CVERecord?id=CVE-2022-1679 Référence CVE CVE-2022-1852 https://www.cve.org/CVERecord?id=CVE-2022-1852 Référence CVE CVE-2022-1882 https://www.cve.org/CVERecord?id=CVE-2022-1882 Référence CVE CVE-2022-20421 https://www.cve.org/CVERecord?id=CVE-2022-20421 Référence CVE CVE-2022-20422 https://www.cve.org/CVERecord?id=CVE-2022-20422 Référence CVE CVE-2022-20566 https://www.cve.org/CVERecord?id=CVE-2022-20

Official advisory
CERT-FR · French · CERTFR-2023-AVI-0121Multiples vulnérabilités dans les produits Siemens

ecord?id=CVE-2021-32948 Référence CVE CVE-2021-41771 https://www.cve.org/CVERecord?id=CVE-2021-41771 Référence CVE CVE-2021-41772 https://www.cve.org/CVERecord?id=CVE-2021-41772 Référence CVE CVE-2021-43336 https://www.cve.org/CVERecord?id=CVE-2021-43336 Référence CVE CVE-2021-43391 https://www.cve.org/CVERecord?id=CVE-2021-43391 Référence CVE CVE-2021-44716 https://www.cve.org/CVERecord?id=CVE-2021-44716 Référence CVE CVE-2021-44717 https://www.cve.org/CVERecord?id=CVE-2021-44717 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-21198 https://www.cve.org/CVERecord?id=CVE-2022-21198 Référence CVE CVE-2022-24675 https://www.cve.org/CVERecord?id=CVE-2022-24675 Référence CVE CVE-2022-24921 https://www.cve.org/CVERecord?id=CVE-2022-24921 Référence CVE CVE-2022-27536 https://www.cve.org/CVERecord?id=CVE-2022-27536 Référence CVE CVE-2022-28327 https://www.cve.org/CVERecord?id=CVE-2022-28327 Référence CVE CVE-2022-30774 https://www.cve.org/CVERecord?id=CVE-2022-30774 Référence CVE CVE-2022-31243 https://www.cve.org/CVERecord?id=CVE

Official advisory
CERT-FR · French · CERTFR-2022-AVI-916Multiples vulnérabilités dans les produits Juniper

e.org/CVERecord?id=CVE-2021-45960 Référence CVE CVE-2021-46143 https://www.cve.org/CVERecord?id=CVE-2021-46143 Référence CVE CVE-2022-0330 https://www.cve.org/CVERecord?id=CVE-2022-0330 Référence CVE CVE-2022-0492 https://www.cve.org/CVERecord?id=CVE-2022-0492 Référence CVE CVE-2022-0778 https://www.cve.org/CVERecord?id=CVE-2022-0778 Référence CVE CVE-2022-0847 https://www.cve.org/CVERecord?id=CVE-2022-0847 Référence CVE CVE-2022-1271 https://www.cve.org/CVERecord?id=CVE-2022-1271 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-22192 https://www.cve.org/CVERecord?id=CVE-2022-22192 Référence CVE CVE-2022-22199 https://www.cve.org/CVERecord?id=CVE-2022-22199 Référence CVE CVE-2022-22201 https://www.cve.org/CVERecord?id=CVE-2022-22201 Référence CVE CVE-2022-22208 https://www.cve.org/CVERecord?id=CVE-2022-22208 Référence CVE CVE-2022-22211 https://www.cve.org/CVERecord?id=CVE-2022-22211 Référence CVE CVE-2022-22218 https://www.cve.org/CVERecord?id=CVE-2022-22218 Référence CVE CVE-2022-22220 https://www.cve.org/CVERecord?id=CVE

Official advisory
CERT-FR · French · CERTFR-2022-AVI-570Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-3712 https://www.cve.org/CVERecord?id=CVE-2021-3712 Référence CVE CVE-2021-44228 https://www.cve.org/CVERecord?id=CVE-2021-44228 Référence CVE CVE-2021-45046 https://www.cve.org/CVERecord?id=CVE-2021-45046 Référence CVE CVE-2021-45105 https://www.cve.org/CVERecord?id=CVE-2021-45105 Référence CVE CVE-2022-0778 https://www.cve.org/CVERecord?id=CVE-2022-0778 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-22576 https://www.cve.org/CVERecord?id=CVE-2022-22576 Référence CVE CVE-2022-27774 https://www.cve.org/CVERecord?id=CVE-2022-27774 Référence CVE CVE-2022-27775 https://www.cve.org/CVERecord?id=CVE-2022-27775 Référence CVE CVE-2022-27776 https://www.cve.org/CVERecord?id=CVE-2022-27776 Gestion détaillée du document le 20 juin 2022 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr f

Official advisory
CERT-FR · French · CERTFR-2022-AVI-411Multiples vulnérabilités dans OpenSSL

De multiples vulnérabilités ont été découvertes dans OpenSSL. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, un déni de service et un contournement de la politique de sécurité.

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
SIMATIC 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); SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0); SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Update to V3.1.5 or later version
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 3 May 2022 · Last source change 17 Sept 2024, 04:19 UTC · CWE-327 · Use of a Broken or Risky Cryptographic Algorithm

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-2698
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2022-2698↗Vendor CSAF · Siemens ProductCERT↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-1434 · cve.blacktree.nl