Simatic Cp443 1 Opc Ua FirmwareOperating system · Siemens

CVE-2019-6575

HIGH · 7.5 CVSS v3.1 Published 2019-04-17
Fix available
A fix is available. Upgrade to 2.7 or later.
See remediation →
84/100
Remediation priority · High
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 SIMATIC CP 443-1 OPC UA (All versions), SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants) (All versions < V2.7), SIMATIC HMI Comfort Outdoor Panels 7" & 15" (incl. SIPLUS variants) (All versions < V15.1 Upd 4), SIMATIC HMI Comfort Panels 4" - 22" (incl. SIPLUS variants) (All versions < V15.1 Upd 4), SIMATIC HMI KTP Mobile Panels KTP400F, KTP700, KTP700F, KTP900 and KTP900F (All versions < V15.1 Upd 4), SIMATIC IPC DiagMonitor (All versions < V5.1.3), SIMATIC NET PC Software V13 (All versions), SIMATIC NET PC Software V14 (All versions < V14 SP1 Update 14), SIMATIC NET PC Software V15 (All versions), SIMATIC RF188C (All versions < V1.1.0), SIMATIC RF600R family (All versions < V3.2.1), SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions >= V2.5 < V2.6.1), SIMATIC S7-1500 Software Controller (All versions between V2.5 (including) and V2.7 (excluding)), SIMATIC WinCC OA (All versions < V3.15 P018), SIMATIC WinCC Runtime Advanced (All versions < V15.1 Upd 4), SINEC NMS (All versions < V1.0 SP1), SINEMA Server (All versions < V14 SP2), SINUMERIK OPC UA Server (All versions < V2.1), TeleControl Server Basic (All versions < V3.1.1). Specially crafted network packets sent to affected devices on port 4840/tcp could allow an unauthenticated remote attacker to cause a denial of service condition of the OPC communication or crash the device. The security vulnerability could be exploited by an attacker with network access to the affected systems. Successful exploitation requires no system privileges and no user interaction. An attacker could use the vulnerability to compromise availability of the OPC communication.

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

Vulnerability in multiple Siemens SIMATIC and OPC UA-enabled products allows unauthenticated remote attackers to send specially crafted packets to port 4840/tcp, causing denial of service of OPC communication or device crash. Exploitation requires network access but no privileges or user interaction.

MitigationApply vendor-supplied patches/upgrades to the specific versions mentioned (e.g., S7-1500 to V2.6.1 or V2.7+, HMI panels to V15.1 Upd 4+, WinCC OA to V3.15 P018+). If patches unavailable, restrict network access to port 4840/tcp via firewalls or segmentation.

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
Simatic Cp443 1 Opc Ua FirmwareOperating system
Affected:all versions
Simatic Et 200 Open Controller Cpu 1515sp Pc2 FirmwareOperating system
Affected:< 2.7
Simatic Ipc Diagmonitor FirmwareOperating system
Affected:all versions
Simatic Net Pc Software FirmwareOperating system
Affected:all versions
Simatic Rf188c FirmwareOperating system
Affected:all versions
Simatic Rf600r FirmwareOperating system
Affected:all versions
Simatic S7 1500 FirmwareOperating system
Affected:<= 2.5
Opc Unified ArchitectureApplication
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
High

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

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 SIMATIC or OPC UA product
    Review system inventory or installed software list for any of these: Simatic Cp443 1 OPC UA, Simatic ET 200 Open Controller CPU 1515SP PC2, Simatic IPC Diagmonitor, Simatic Net PC Software, Simatic RF188C, Simatic RF600R, Simatic S7-1500, or Siemens OPC Unified Architecture.
    Affected if Any of the affected products from the list is installed on the system.
  2. Check S7-1500 firmware version
    Access the S7-1500 CPU via TIA Portal or web interface and retrieve the firmware version from the device properties or online diagnostics.
    Affected if Firmware version is 2.5 or lower.
  3. Check ET 200 Open Controller firmware version
    Access the ET 200 Open Controller via TIA Portal or onboard web server and retrieve the firmware version from device information.
    Affected if Firmware version is below 2.7.
  4. Verify OPC UA port 4840/tcp is listening
    Run command 'netstat -an | findstr :4840' or 'ss -tlnp | grep 4840' on the target system to check if port 4840 is in LISTEN state.
    Affected if Port 4840/tcp is open and listening for OPC UA connections.
  5. Check network accessibility of OPC UA service
    From an external host, run 'telnet <target_ip> 4840' or 'nmap -p 4840 <target_ip>' to verify the port is reachable over the network.
    Affected if Port 4840/tcp is accessible from untrusted network segments.

The system is affected if it runs any of the listed Siemens products with a vulnerable firmware version (or any version for fully affected products) AND has port 4840/tcp open and 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 2.7 or later
Fixed in 2.7
Interim mitigation

Apply vendor-supplied patches/upgrades to the specific versions mentioned (e.g., S7-1500 to V2.6.1 or V2.7+, HMI panels to V15.1 Upd 4+, WinCC OA to V3.15 P018+). If patches unavailable, restrict network access to port 4840/tcp via firewalls or segmentation.

Fix this in Simatic Cp443 1 Opc Ua Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2019-6575 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