CVE-2019-19281
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 · uneditedA vulnerability has been identified in SIMATIC ET 200SP Open Controller CPU 1515SP PC2 (incl. SIPLUS variants) (All versions >= V2.5 and < V20.8), SIMATIC S7-1500 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions >= V2.5 and < V2.8), SIMATIC S7-1500 Software Controller (All versions >= V2.5 and < V20.8). Affected devices contain a vulnerability that allows an unauthenticated attacker to trigger a Denial-of-Service condition. The vulnerability can be triggered if specially crafted UDP packets are sent to 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 the device availability.
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 confidenceUnauthenticated attackers can send specially crafted UDP packets to affected Siemens SIMATIC S7-1500 CPU family, ET 200SP Open Controller, and S7-1500 Software Controller devices, causing a denial-of-service condition that compromises device availability.
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>= 2.5, < 20.8>= 2.5, < 2.8>= 2.5, < 2.8>= 2.5, < 2.8>= 2.5, < 2.8>= 2.5, < 2.8>= 2.5, < 2.8>= 2.5, < 2.8CVSS 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 device modelAccess the device via TIA Portal or web interface, or check the device nameplate to confirm the exact CPU model (e.g., CPU 1511 1 PN, CPU 1515SP PC2, etc.)Affected if The device is one of the following: ET 200SP Open Controller CPU 1515SP PC2, S7-1500 CPU 1511 1 PN, CPU 1513 1 PN, CPU 1515 2 PN, CPU 1516 3 PN, CPU 1516 3 DP, CPU 1517 3 PN, or CPU 1517 3 DP
-
Check firmware versionIn TIA Portal, go to Online & Diagnostics > Diagnostics > Overview, or access the device web page and navigate to the firmware version informationAffected if Firmware version is 2.5 or higher but below 2.8 for S7-1500 CPU family, or below 20.8 for ET 200SP Open Controller
-
Verify network exposure to UDPReview network configuration and firewall rules to determine if the device is directly accessible on UDP ports from untrusted networksAffected if The device has UDP ports exposed to untrusted or external networks without firewall filtering
Device is affected if it is one of the listed models AND runs firmware in the vulnerable version range (>=2.5 but <2.8 for S7-1500, or <20.8 for ET 200SP) AND has UDP network accessibility from untrusted sources.
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 data2.820.8
Upgrade to V20.8 (ET 200SP and S7-1500 Software Controller) or V2.8 (S7-1500 CPU family), or restrict network access to UDP ports and implement firewall controls to block untrusted traffic.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.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 $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19281 — 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-19281 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