dbcve.org
Opcenter Execution DiscreteApplication · Siemens

CVE-2020-7588

MEDIUM · 5.3 CVSS v3.1 Published 2020-07-14
Fix available
A fix is available. Upgrade to 3.2 / 11.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 a specially crafted packet to the affected service could cause a partial remote denial-of-service, that would cause the service to restart itself.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A remote denial-of-service vulnerability exists in multiple Siemens industrial software products (Opcenter, SIMATIC IT, SIMATIC PCS neo, SIMATIC STEP 7/TIA Portal, SIMOCODE ES, Soft Starter ES). An unauthenticated remote attacker can send specially crafted packets to the affected service, causing it to restart unexpectedly.

MitigationApply the vendor-supplied updates: upgrade to Opcenter Execution Discrete/Foundation/Process V3.2 or later, Opcenter Intelligence V3.3 or later, Opcenter Quality V11.3 or later, SIMATIC IT LMS V2.6 or later, SIMATIC IT Production Suite V8.0 or later, SIMATIC PCS neo V3.0 SP1 or later, SIMATIC STEP 7 V15.1 Update 5 or later, SIMATIC STEP 7 V16 Update 2 or later, and corresponding updates for SIMOCODE ES and Soft Starter ES. Additionally, network segmentation and firewall rules should limit exposure of affected services to trusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Opcenter Execution DiscreteApplication
Affected:< 3.2
Opcenter Execution FoundationApplication
Affected:< 3.2
Opcenter Execution ProcessApplication
Affected:< 3.2
Opcenter IntelligenceApplication
Affected:all versions
Opcenter QualityApplication
Affected:< 11.3
Opcenter Rd\&lApplication
Affected:= 8.0
Simatic It LmsApplication
Affected:all versions
Simatic It Production SuiteApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Siemens industrial software
    Review installed programs on the system or check the Siemens Software Lifecycle Management database for installed Siemens industrial software products such as Opcenter Execution, Opcenter Intelligence, Opcenter Quality, SIMATIC IT LMS, or SIMATIC IT Production Suite.
    Affected if Any of the affected products listed in the CVE are installed.
  2. Determine installed version of Opcenter products
    Open the Siemens Opcenter application or check the installed programs list, and locate the version number for Opcenter Execution Discrete, Opcenter Execution Foundation, Opcenter Execution Process, Opcenter Quality, or Opcenter Intelligence.
    Affected if For Opcenter Execution Discrete/Foundation/Process: version is below 3.2. For Opcenter Quality: version is below 11.3. For Opcenter Intelligence: any version found (all versions affected).
  3. Determine installed version of SIMATIC IT products
    Check the installed programs list or SIMATIC IT application properties for SIMATIC IT LMS or SIMATIC IT Production Suite version numbers.
    Affected if Any version of SIMATIC IT LMS or SIMATIC IT Production Suite is installed (all versions affected).
  4. Check network exposure of affected services
    Review firewall rules and network configuration to determine if the Siemens industrial software services are exposed to untrusted networks or the internet.
    Affected if The affected service is reachable from untrusted network segments (the vulnerability is remotely exploitable via network packets).

The environment is affected if any Siemens industrial software product from the CVE list is installed with a version matching the affected ranges AND the service is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 3.2 / 11.3 or later
Fixed in 3.211.3
Interim mitigation

Apply the vendor-supplied updates: upgrade to Opcenter Execution Discrete/Foundation/Process V3.2 or later, Opcenter Intelligence V3.3 or later, Opcenter Quality V11.3 or later, SIMATIC IT LMS V2.6 or later, SIMATIC IT Production Suite V8.0 or later, SIMATIC PCS neo V3.0 SP1 or later, SIMATIC STEP 7 V15.1 Update 5 or later, SIMATIC STEP 7 V16 Update 2 or later, and corresponding updates for SIMOCODE ES and Soft Starter ES. Additionally, network segmentation and firewall rules should limit exposure of affected services to trusted networks.

Fix this in Opcenter Execution Discrete Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7588 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7588 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data