Siemens SIMATIC S7-1200 CPU 1211C Firmware 4.4.0

CPE Details

Siemens SIMATIC S7-1200 CPU 1211C Firmware 4.4.0
4.4.0
2020-10-30
10h11 +00:00
2020-10-30
10h11 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:o:siemens:simatic_s7-1200_cpu_1211c_firmware:4.4.0:*:*:*:*:*:*:*

Informations

Vendor

siemens

Product

simatic_s7-1200_cpu_1211c_firmware

Version

4.4.0

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2021-40365 2022-12-12 23h00 +00:00 Affected devices don't process correctly certain special crafted packets sent to port 102/tcp, which could allow an attacker to cause a denial of service in the device.
7.5
High
CVE-2021-44693 2022-12-12 23h00 +00:00 Affected devices don't process correctly certain special crafted packets sent to port 102/tcp, which could allow an attacker to cause a denial of service in the device.
7.5
High
CVE-2021-44694 2022-12-12 23h00 +00:00 Affected devices don't process correctly certain special crafted packets sent to port 102/tcp, which could allow an attacker to cause a denial of service in the device.
7.5
High
CVE-2021-44695 2022-12-12 23h00 +00:00 Affected devices don't process correctly certain special crafted packets sent to port 102/tcp, which could allow an attacker to cause a denial of service in the device.
7.5
High
CVE-2021-3449 2021-03-25 14h25 +00:00 An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).
5.9
Medium