CVE-2018-19016
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 · uneditedRockwell Automation EtherNet/IP Web Server Modules 1756-EWEB (includes 1756-EWEBK) Version 5.001 and earlier, and CompactLogix 1768-EWEB Version 2.005 and earlier. A remote attacker could send a crafted UDP packet to the SNMP service causing a denial-of-service condition to occur until the affected product is restarted.
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 confidenceDenial-of-service vulnerability in the SNMP service of Rockwell Automation EtherNet/IP Web Server Modules (1756-EWEB and 1768-EWEB). A remote attacker can send a crafted UDP packet to the SNMP service, causing the device to become unresponsive and require a restart to recover.
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<= 5.001<= 2.005CVSS 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.0/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 module or check the device inventory to confirm whether the device is a 1756-EWEB or 1768-EWEB EtherNet/IP Web Server ModuleAffected if The device is a 1756-EWEB or 1768-EWEB module
-
Check the installed firmware versionAccess the module through its web interface or use RSLinx Classic to view the firmware version. Compare your version against the affected ranges: 1756-EWEB <= 5.001 or 1768-EWEB <= 2.005Affected if The firmware version is 5.001 or earlier for 1756-EWEB, or 2.005 or earlier for 1768-EWEB
-
Verify if SNMP is enabledLog into the module web interface and navigate to the SNMP configuration settings. Check the SNMP service status or review the module configuration via RSLinxAffected if SNMP is enabled and configured on the module
-
Confirm UDP 161/162 accessibilityScan the network to verify whether UDP ports 161 and 162 on the module are reachable from untrusted network segments. Use a network scanner or firewall logs to check for external access attemptsAffected if SNMP UDP ports are exposed to untrusted networks or the internet
The environment is affected if the device is a 1756-EWEB (firmware <= 5.001) or 1768-EWEB (firmware <= 2.005) with SNMP enabled and accessible to potential attackers.
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 dataUpdate to patched firmware versions when available. Until then, restrict network access to SNMP ports (UDP 161/162) via firewall rules or disable SNMP if not operationally required. Consider network segmentation to limit exposure of affected devices.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19016 — 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-2018-19016 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