Siprotec 4Application · Siemens

CVE-2019-19279

HIGH · 7.5 CVSS v3.1 Published 2020-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 SIPROTEC 4 and SIPROTEC Compact relays equipped with EN100 Ethernet communication modules (All versions). Specially crafted packets sent to port 50000/UDP of the EN100 Ethernet communication modules could cause a Denial-of-Service of the affected device. A manual reboot is required to recover the service of the device. At the time of advisory publication no public exploitation of this security vulnerability was known to Siemens.

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

A Denial-of-Service vulnerability exists in SIPROTEC 4 and SIPROTEC Compact relays with EN100 Ethernet communication modules. Attackers can send specially crafted UDP packets to port 50000, causing the device to become unresponsive and requiring a manual reboot to restore service.

MitigationApply network segmentation and firewall rules to restrict unauthorized access to port 50000/UDP. Contact Siemens for firmware updates to address this vulnerability in EN100 modules.

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
Siprotec 4Application
Affected:all versions
Siprotec CompactApplication
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 SIPROTEC devices on the network
    Scan the network for devices with product identifiers containing 'SIPROTEC 4' or 'SIPROTEC Compact' or conduct an inventory of industrial control devices. Check device nameplates, management interfaces, or PLC/SCADA system documentation for these product names.
    Affected if Any SIPROTEC 4 or SIPROTEC Compact relay devices are present in the environment
  2. Confirm EN100 module presence
    Access the web-based or management interface of the SIPROTEC device and navigate to the communication module configuration. Look for 'EN100' or 'EN100 Ethernet' module listed in the hardware or module status.
    Affected if An EN100 Ethernet communication module is installed or configured on the device
  3. Verify UDP port 50000 exposure
    Perform a network port scan targeting the SIPROTEC devices for UDP port 50000, or review firewall and network segmentation configurations to determine if port 50000/UDP is open to untrusted networks.
    Affected if Port 50000/UDP is reachable from any network segment that contains untrusted or external systems
  4. Check network access controls
    Review firewall rules, ACLs, or network segmentation policies that govern traffic to the SIPROTEC devices. Verify whether port 50000/UDP traffic is restricted to authorized management stations or trusted networks only.
    Affected if Port 50000/UDP has no firewall restrictions or is accessible from less trusted network zones

If any SIPROTEC 4 or SIPROTEC Compact device with an EN100 module exists and port 50000/UDP is accessible from an untrusted network segment, the environment is affected by this CVE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply network segmentation and firewall rules to restrict unauthorized access to port 50000/UDP. Contact Siemens for firmware updates to address this vulnerability in EN100 modules.

Fix this in Siprotec 4 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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