CVE-2019-10953
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 · uneditedABB, Phoenix Contact, Schneider Electric, Siemens, WAGO - Programmable Logic Controllers, multiple versions. Researchers have found some controllers are susceptible to a denial-of-service attack due to a flood of network packets.
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 confidenceMultiple programmable logic controller (PLC) models from ABB, Phoenix Contact, Schneider Electric, Siemens, and WAGO are susceptible to denial-of-service attacks. The vulnerability allows remote attackers to crash or render controllers unresponsive by flooding them with excessive network packets, likely causing resource exhaustion or processing failures.
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< 1.10.0.0all versionsall versionsall versionsall versionsall versionsCVSS 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 PLC hardware models on your networkReview network documentation, scan for device fingerprints, or physically inspect PLC equipment to determine if any of the following models are present: ABB PM554-TP-ETH, Phoenix Contact ILC 151 ETH, Schneider Electric Modicon M221, Siemens 6ES7211-1AE40-0xB0, Siemens 6ES7314-6EH04-0AB0, Siemens 6ED1052-1CC01-0BA8, WAGO KNX IP, or WAGO PFC100Affected if Any of these specific PLC models are found on the network
-
Check the firmware version of Schneider Electric Modicon M221Access the PLC management interface or use vendor-specific diagnostic tools to retrieve the current firmware version. Compare against the vulnerable range of < 1.10.0.0Affected if Firmware version is lower than 1.10.0.0 for Modicon M221
-
Verify network accessibility of PLC devicesDetermine if PLC devices are directly exposed to untrusted networks or the internet by reviewing firewall rules, network segmentation, and ACL configurations. Check if external network traffic can reach the PLC network segmentAffected if PLC devices are accessible from untrusted networks without firewall protection
-
Check for signs of resource exhaustion on PLCsMonitor PLC performance metrics such as CPU usage, memory consumption, and network interface statistics. Look for unexpected crashes, unresponsiveness, or excessive network packet processingAffected if PLCs exhibit sudden crashes, unresponsiveness, or resource exhaustion without legitimate cause
-
Review network traffic for packet flood patternsAnalyze network logs or packet captures for unusually high volumes of traffic directed at PLC devices, which may indicate exploitation attemptsAffected if Abnormal packet flood patterns targeting PLC devices are detected
Your environment is affected if you have any of the listed PLC models (ABB PM554-TP-ETH, Phoenix Contact ILC 151 ETH, Schneider Modicon M221 < 1.10.0.0, Siemens variants, or WAGO KNX IP/PFC100) exposed on accessible networks.
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.10.0.0
Implement network segmentation and firewall rules to restrict unauthorized traffic to PLC networks. Contact affected vendors for specific firmware patches and apply vendor-recommended DoS mitigations. Consider deploying intrusion detection systems to identify and block anomalous packet floods.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10953 — 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-10953 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