CVE-2019-10936
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 · uneditedAffected devices improperly handle large amounts of specially crafted UDP packets. This could allow an unauthenticated remote attacker to trigger a denial of service condition.
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 confidenceAffected devices fail to properly handle large volumes of specially crafted UDP packets, allowing an unauthenticated remote attacker to send these packets and trigger a denial of service condition by exhausting device resources or causing crashes.
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 dataall versionsall versions< 4.6= 4.6< 1.2.0all versionsall versions< 4.3.0< 4.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the physical device labeling, check Siemens TIA Portal project inventory, or query the device via SNMP/Profinet for its product identification (e.g., DK Standard Ethernet Controller, EK ERTEC 200, SIMATIC ET 200AL, SIMATIC ET 200M, etc.)Affected if The device matches any of the affected product names: DK Standard Ethernet Controller, EK ERTEC 200, EK ERTEC 200p, SIMATIC CFU PA, SIMATIC ET 200AL, SIMATIC ET 200M, SIMATIC ET 200MP IM 155-5 PN BA, or SIMATIC ET 200MP IM 155-5 PN HF
-
Check the installed firmware versionAccess the device via its web interface, use Siemens STEP 7/TIA Portal to read the firmware version, or query the device through its management interface (console, SNMP) for the firmware revisionAffected if The firmware version is below the safe threshold: ERTEC 200p < 4.6 or = 4.6, CFU PA < 1.2.0, ET 200MP PN BA < 4.3.0, ET 200MP PN HF < 4.4.0, or for products listed as 'all versions' any version is affected
-
Verify UDP service is enabled and exposedCheck device network configuration for open UDP ports, use netstat or port scanning tools to detect UDP listeners on the device, review the device's Profinet/ethernet communication settingsAffected if The device has UDP services enabled and is accessible on the network (the vulnerability is triggered by specially crafted UDP packets hitting the device)
-
Review network exposure of affected devicesCheck firewall rules, network segmentation, and ACLs protecting the device; determine if the device UDP interfaces are reachable from untrusted networks or the internetAffected if The device UDP interfaces are reachable from untrusted or external network segments without UDP rate limiting or filtering in place
You are affected if your device is one of the listed Siemens products with a vulnerable firmware version and its UDP interfaces are network-accessible without protective filtering.
Generated from the published advisory. Verify against your own configuration.
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 data1.2.04.3.04.4.0
Implement network-level protections such as UDP rate limiting, ingress traffic filtering, or firewall rules to block or throttle suspicious UDP traffic patterns; consider network segmentation to isolate affected devices.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10936 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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