CVE-2019-13942
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 EN100 Ethernet module DNP3 variant (All versions), EN100 Ethernet module IEC 61850 variant (All versions < V4.37), EN100 Ethernet module IEC104 variant (All versions), EN100 Ethernet module Modbus TCP variant (All versions), EN100 Ethernet module PROFINET IO variant (All versions). An unauthorized user could exploit a buffer overflow vulnerability in the webserver. Specially crafted packets sent could cause a Denial-of-Service condition and if certain conditions are met, the affected devices must be restarted manually to fully recover. At the time of advisory publication no public exploitation of this security vulnerability was known.
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 confidenceBuffer overflow vulnerability in the webserver component of ABB EN100 Ethernet modules across multiple protocol variants (DNP3, IEC 61850, IEC104, Modbus TCP, PROFINET IO). An unauthenticated remote attacker can send specially crafted packets to cause a Denial-of-Service condition, potentially requiring manual device restart for full recovery.
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 versions< 4.37all 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 the device model and firmware variantAccess the EN100 module's web interface or use SNMP/serial console to retrieve the device identity information. Look for 'EN100' in the model name and note the firmware variant (DNP3 TCP, IEC 61850, IEC104, Modbus TCP, or PROFINET IO).Affected if The device is not an EN100 Ethernet module or the variant is not one of the five affected types.
-
Determine the installed firmware versionIn the web interface, navigate to the status or system information page to view the firmware version. For IEC 61850 variants, the version is displayed as Vx.xx (for example, V4.36 or V4.37).Affected if The firmware version cannot be determined or the device is not reachable.
-
Verify the webserver component is enabledAccess the web interface on the EN100 module (typically via HTTP on port 80). If a login page or status page loads, the webserver is active. Check the web server configuration settings in the administration or network settings section.Affected if The webserver is disabled or inaccessible (no HTTP response on standard ports).
-
Confirm the affected variant and version rangeCompare the identified variant and firmware version against the affected ranges: DNP3 TCP (all versions), IEC 61850 (< 4.37), IEC104 (all versions), Modbus TCP (all versions), PROFINET IO (all versions).Affected if The variant is IEC 61850 with version 4.37 or later, or the variant is not one of the five affected types.
The environment is affected if an EN100 Ethernet module with an affected variant (DNP3 TCP, IEC 61850, IEC104, Modbus TCP, or PROFINET IO) has its webserver enabled and, for IEC 61850, runs firmware versions prior to V4.37.
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 data4.37
Implement network segmentation to restrict access to the EN100 webserver interface from untrusted networks. Apply vendor patches when available; for IEC 61850 variant, upgrade to V4.37 or later. Consider disabling the webserver if not operationally required.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13942 — 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-13942 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