CVE-2022-27640 json
A vulnerability has been identified in SIMATIC CP 442-1 RNA (All versions < V1.5.18), SIMATIC CP 443-1 RNA (All versions < V1.5.18).
published 2022-05-10 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-32141
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in SIMATIC CP 442-1 RNA (All versions < V1.5.18), SIMATIC CP 443-1 RNA (All versions < V1.5.18). The affected devices improperly handles excessive ARP broadcast requests. This could allow an attacker to create a denial of service condition by performing ARP storming attacks, which can cause the device to reboot.
Patch / fix
- siemens simatic_cp_442-1_rna_firmware 1.5.18
- siemens simatic_cp_443-1_rna_firmware 1.5.18
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-22-132-11 updated cvss 7.4
Siemens SIMATIC CP 44x-1 RNA
-
Siemens SIMATIC CP 442-1 RNA <V1.5.18affected: fixed in V1.5.18 support.industry.siemens.com
-
Siemens SIMATIC CP 443-1 RNA <V1.5.18affected: fixed in V1.5.18 support.industry.siemens.com
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 6.1 | AV:A/AC:L/Au:N/C:N/I:N/A:C |
Affected products
- Siemens SIMATIC CP 442-1 RNA
- Siemens SIMATIC CP 443-1 RNA
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-480937.pdf
patch, vendor-advisory
Sources
- CVE List CVE-2022-27640
- NVD CVE-2022-27640
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.