CVE-2019-13943
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). The web interface could allow Cross-Site Scripting (XSS) attacks if an attacker is able to modify content of particular web pages, causing the application to behave in unexpected ways for legitimate users. Successful exploitation does not require for an attacker to be authenticated to the web interface. This could allow the attacker to read or modify contents of the web application. 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 · high confidenceCross-Site Scripting (XSS) vulnerability in the web interface of ABB EN100 Ethernet module multiple variants (DNP3, IEC 61850, IEC104, Modbus TCP, PROFINET IO). The vulnerability allows unauthenticated attackers to inject malicious scripts into web pages, potentially reading or modifying web application contents.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Confirm EN100 web interface is enabledAccess the EN100 module's IP address via HTTP/HTTPS in a web browser. If a login page or web configuration panel loads, the web interface is enabled.Affected if The web interface is accessible and the module uses one of the affected firmware variants (DNP3 TCP, IEC 61850, IEC104, Modbus TCP, PROFINET IO).
-
Identify the firmware variantLocate the product model number or firmware variant information in the web interface (usually under Device Info, Status, or System Information pages) or check the physical device label. Variants include: DNP3 TCP, IEC 61850, IEC104, Modbus TCP, PROFINET IO.Affected if The device is any EN100 variant other than IEC 61850 (see next step for that exception).
-
Check firmware version for IEC 61850 variantIn the web interface, navigate to the firmware version or software version field (typically found under System, Status, or About sections). Compare the displayed version number to the affected range.Affected if The firmware version is lower than 4.37 (e.g., 4.36, 4.35, etc.).
-
Check firmware version for non-IEC 61850 variantsIn the web interface, locate the firmware or software version information (usually under Device Information, Status, or Help pages).Affected if The device runs DNP3 TCP, IEC104, Modbus TCP, or PROFINET IO variant at any version (all versions are affected).
-
Verify network exposure of the web interfaceCheck if the EN100 web interface IP is accessible from untrusted networks by reviewing network firewall rules or performing a port scan (ports 80/443) from an external system.Affected if The web interface is exposed to untrusted networks without segmentation, allowing unauthenticated attackers to reach the XSS payload.
The environment is affected if an EN100 Ethernet module with an affected variant (DNP3 TCP, IEC 61850 < 4.37, IEC104, Modbus TCP, or PROFINET IO) has its web interface enabled and reachable.
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
Apply vendor firmware updates (IEC 61850 variant requires V4.37 or later); for other variants, contact ABB for patch availability. Implement network segmentation to limit web interface exposure.
- Consultation4.0 h
- Implementation8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13943 — 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-13943 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