dbcve.org
Opcenter Execution DiscreteApplication · Siemens

CVE-2020-7587

HIGH · 8.2 CVSS v3.1 Published 2020-07-14
Fix available
A fix is available. Upgrade to 2.6 / 3.2 or later.
See remediation →
91/100
Remediation priority · Urgent
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 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.

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 · moderate confidence

Multiple Siemens industrial software products contain a vulnerability in their network service components that allows remote attackers to send specially crafted packets. This causes a partial denial-of-service (service restart) and can leak random information from the affected service.

MitigationApply vendor-supplied updates to reach the specified minimum versions (V3.2 for Opcenter Execution products, V3.3 for Opcenter Intelligence, V11.3 for Opcenter Quality, etc.). As a compensating control, restrict network access to affected services to trusted sources only.

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:< 3.3
Opcenter QualityApplication
Affected:< 11.3
Opcenter Rd\&lApplication
Affected:= 8.0
Simatic It LmsApplication
Affected:< 2.6
Simatic It Production SuiteApplication
Affected:< 8.0

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
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 product
    Review installed programs or check the program's About/Version information in the application UI, or query the Windows Registry under HKLM\SOFTWARE\Siemens for installed components
    Affected if The installed product matches any of: Opcenter Execution Discrete, Opcenter Execution Foundation, Opcenter Execution Process, Opcenter Intelligence, Opcenter Quality, Opcenter Rd&L, Simatic It Lms, or Simatic It Production Suite
  2. Determine installed version of the Siemens product
    Access the product's version information through the application Help menu, check installation directories for version files, or use Siemens installation management tools if available
    Affected if The version is below the safe threshold: < 3.2 for Opcenter Execution products, < 3.3 for Opcenter Intelligence, < 11.3 for Opcenter Quality, = 8.0 for Opcenter Rd&L, < 2.6 for Simatic It Lms, or < 8.0 for Simatic It Production Suite
  3. Verify network service component is running and exposed
    Use netstat or TCPView to check for listening ports associated with the Siemens product services (consult product documentation for specific port numbers), or review firewall rules governing inbound traffic to the host
    Affected if The network service component is listening on an accessible network interface and accepts remote connections from untrusted sources
  4. Check for recent service restarts or anomalous logs
    Review Windows Event Viewer logs under Application and System logs for unexpected service restarts, or check Siemens product-specific logs for error entries around the time of incidents
    Affected if Service has experienced unexplained restarts or error messages indicating information leaks or packet processing failures

A defender is affected if any Siemens Opcenter or Simatic IT product listed is installed with a version number below the safe threshold and its network service component is accessible to untrusted network sources.

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 2.6 / 3.2 / 3.3 or later
Fixed in 2.63.23.3
Interim mitigation

Apply vendor-supplied updates to reach the specified minimum versions (V3.2 for Opcenter Execution products, V3.3 for Opcenter Intelligence, V11.3 for Opcenter Quality, etc.). As a compensating control, restrict network access to affected services to trusted sources only.

Fix this in Opcenter Execution Discrete Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7587 — 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-7587 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