LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15782: A vulnerability has been identified in SIMATIC Drive Controller family (All versions < V2.9.2), SIMATIC ET...

A vulnerability has been identified in SIMATIC Drive Controller family (All versions < V2.9.2), SIMATIC ET 200SP Open Controller CPU 1515SP PC (incl. SIPLUS variants) (All versions), SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants) (All versions < V21.9), SIMATIC S7-1200 CPU family (incl. SIPLUS variants) (All versions < V4.5.0), SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions < V2.9.2), SIMATIC S7-1500 Software Controller (All versions < V21.9), SIMATIC S7-PLCSIM Advanced (All versions < V4.0), SINAMICS PERFECT HARMONY GH180 Drives (Drives manufactured before 2021-08-13), SINUMERIK MC (All versions < V6.15), SINUMERIK ONE (All versions < V6.15). Affected devices are vulnerable to a memory protection bypass through a specific operation. A remote unauthenticated attacker with network access to port 102/tcp could potentially write arbitrary data and code to protected memory areas or read sensitive data to launch further attacks.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This Siemens industrial-control vulnerability can let an unauthenticated network attacker reach protected device memory through port 102/tcp. On affected PLCs, controllers, drives, CNC systems, and simulation software, that could mean data theft, process disruption, or unauthorized code/data changes.

Executive priority

Treat this as urgent for industrial environments. The business risk is unauthorized manipulation or disclosure on critical automation assets. Prioritize exposed production systems first, especially those reachable beyond tightly controlled OT networks.

Technical view

CVE-2020-15782 is a memory protection bypass affecting multiple Siemens SIMATIC, SINAMICS, and SINUMERIK products. CVSS 3.1 is 9.8. The source states a remote unauthenticated attacker with network access to 102/tcp could read sensitive data or write arbitrary data and code to protected memory areas.

Likely exposure

Exposure is most likely where affected Siemens automation assets expose S7 communication on 102/tcp to broader plant, enterprise, vendor, or remote-access networks. Internet exposure would materially increase urgency, but the provided bundle does not prove active internet exploitation.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The attack preconditions are still serious: remote, unauthenticated network access, low complexity, and no user interaction.

Researcher notes

Key uncertainty is remediation detail for entries listed as all versions or manufacture-date constrained. The bundle provides severity, attack vector, affected ranges, and Siemens advisory URLs, but not proof of exploitation or complete product-specific fix instructions.

Mitigation direction

  • Upgrade affected Siemens products to fixed versions where the bundle names version thresholds.
  • For products listed as all versions, check Siemens advisories for product-specific guidance.
  • Restrict access to 102/tcp to required engineering and control hosts.
  • Prioritize segmentation for PLC, drive, CNC, and simulation environments.
  • Review SINAMICS GH180 drive manufacture dates against the 2021-08-13 cutoff.

Validation and detection

  • Inventory Siemens SIMATIC, SINAMICS, and SINUMERIK assets from the affected product list.
  • Confirm firmware or software versions against the listed affected thresholds.
  • Identify hosts or networks that can reach affected assets on 102/tcp.
  • Review remote access paths into control networks for unintended 102/tcp reachability.
  • Document products with no fixed version named and track Siemens guidance.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-119: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-15782 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-15782Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SiemensSIMATIC Drive Controller familyAll versions < V2.9.2Listed
SiemensSIMATIC ET 200SP Open Controller CPU 1515SP PC (incl. SIPLUS variants)All versionsListed
SiemensSIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants)All versions < V21.9Listed
SiemensSIMATIC S7-1200 CPU family (incl. SIPLUS variants)All versions < V4.5.0Listed
SiemensSIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants)All versions < V2.9.2Listed
SiemensSIMATIC S7-1500 Software ControllerAll versions < V21.9Listed
SiemensSIMATIC S7-PLCSIM AdvancedAll versions < V4.0Listed
SiemensSINAMICS PERFECT HARMONY GH180 DrivesDrives manufactured before 2021-08-13Listed
SiemensSINUMERIK MCAll versions < V6.15Listed
SiemensSINUMERIK ONEAll versions < V6.15Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-119 · source CWE mapping

Improper Restriction of Operations within the Bounds of a Memory Buffer

Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.