CVE-2020-7584 json
A vulnerability has been identified in SIMATIC S7-200 SMART CPU family (All versions >= V2.2 < V2.5.1).
published 6y ago modified 4mo ago also EUVD-2020-28709
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in SIMATIC S7-200 SMART CPU family (All versions >= V2.2 < V2.5.1). Affected devices do not properly handle large numbers of new incomming connections and could crash under certain circumstances. An attacker may leverage this to cause a Denial-of-Service situation.
Patch / fix
- siemens simatic_s7-200_smart_sr_cpu_firmware 2.5.1
- siemens simatic_s7-200_smart_st_cpu_firmware 2.5.1
Is CVE-2020-7584 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-20-196-06 updated cvss 7.5
Siemens SIMATIC S7-200 SMART CPU Family
-
Siemens SIMATIC S7-200 SMART CPU family >= <= 2.2, 2.5.1affected: fixed in v2.5.1 support.industry.siemens.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- Siemens AG SIMATIC S7-200 SMART CPU family
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-589181.pdf
vendor-advisory
Sources
- CVE List CVE-2020-7584
- NVD CVE-2020-7584
Fencer Intel 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.