Skip to content
Fencer Vulns
high 8.2

CVE-2020-7587 json

A vulnerability has been identified in Opcenter Execution Discrete (All versions < V3.2), Opcenter Execution Foundation (All versions < V3.…

published 2020-07-14 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-28712

cvss
8.2
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

A vulnerability has been identified in Opcenter Execution Discrete (All versions < V3.2), Opcenter Execution Foundation (All versions < V3.2), Opcenter Execution Process (All versions < V3.2), Opcenter Intelligence (All versions < V3.3), Opcenter Quality (All versions < V11.3), Opcenter RD&L (V8.0), SIMATIC IT LMS (All versions < V2.6), SIMATIC IT Production Suite (All versions < V8.0), SIMATIC Notifier Server for Windows (All versions), SIMATIC PCS neo (All versions < V3.0 SP1), SIMATIC STEP 7 (TIA Portal) V15 (All versions < V15.1 Update 5), SIMATIC STEP 7 (TIA Portal) V16 (All versions < V16 Update 2), SIMOCODE ES V15.1 (All versions < V15.1 Update 4), SIMOCODE ES V16 (All versions < V16 Update 1), Soft Starter ES V15.1 (All versions < V15.1 Update 3), Soft Starter ES V16 (All versions < V16 Update 1). Sending multiple specially crafted packets to the affected service could cause a partial remote denial-of-service, that would cause the service to restart itself. On some cases the vulnerability could leak random information from the remote service.

Patch / fix

  • siemens opcenter_execution_discrete 3.2
  • siemens opcenter_execution_foundation 3.2
  • siemens opcenter_execution_process 3.2
  • siemens opcenter_intelligence 3.3
  • siemens opcenter_quality 11.3
  • siemens simatic_it_lms 2.6
  • siemens simatic_it_production_suite 8.0
  • siemens simatic_pcs_neo 3.0
  • siemens simatic_step_7 15.1
  • siemens simocode_es 15.1
  • siemens soft_starter_es 15.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-20-196-05 updated cvss 6.5

Siemens UMC Stack (Update H)

  • Siemens Opcenter Execution Discrete <V3.2 Siemens Opcenter Execution Foundation <V3.2 Siemens Opcenter Execution Process <V3.2
    affected: fixed in V3.2, mitigation support.sw.siemens.com
  • Siemens Opcenter Intelligence <V3.3
    affected: fixed in V3.3, mitigation support.sw.siemens.com
  • Siemens Opcenter Quality <V11.3
    affected: fixed in V11.3, mitigation support.sw.siemens.com
  • Siemens Opcenter RD&L V8.0
    affected: fixed in V8.1, mitigation support.sw.siemens.com
  • Siemens SIMATIC IT LMS <V2.6
    affected: fixed in V2.6, mitigation support.sw.siemens.com
  • Siemens SIMATIC IT Production Suite <V8.0
    affected: fixed in V8.0, mitigation support.sw.siemens.com
  • Siemens SIMATIC Notifier Server for Windows
    affected: mitigation, no fix planned
  • Siemens SIMATIC PCS neo <V3.0_SP1
    affected: fixed in V3.0, mitigation
show 6 more

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

2.48% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:N/A:P

Affected products

  • Siemens Opcenter Execution Discrete
  • Siemens Opcenter Execution Foundation
  • Siemens Opcenter Execution Process
  • Siemens Opcenter Intelligence
  • Siemens Opcenter Quality
  • Siemens Opcenter RD&L
  • Siemens SIMATIC IT LMS
  • Siemens SIMATIC IT Production Suite
  • Siemens SIMATIC Notifier Server for Windows
  • Siemens SIMATIC PCS neo
  • Siemens SIMATIC STEP 7 (TIA Portal) V15
  • Siemens SIMATIC STEP 7 (TIA Portal) V16
  • Siemens SIMOCODE ES V15.1
  • Siemens SIMOCODE ES V16
  • Siemens Soft Starter ES V15.1
  • Siemens Soft Starter ES V16

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

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.