CVE-2016-7114
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 Firmware variant PROFINET IO for EN100 Ethernet module : All versions < V1.04.01; Firmware variant Modbus TCP for EN100 Ethernet module : All versions < V1.11.00; Firmware variant DNP3 TCP for EN100 Ethernet module : All versions < V1.03; Firmware variant IEC 104 for EN100 Ethernet module : All versions < V1.21; EN100 Ethernet module included in SIPROTEC Merging Unit 6MU80 : All versions < 1.02.02; SIPROTEC 7SJ686 : All versions < V 4.87; SIPROTEC 7UT686 : All versions < V 4.02; SIPROTEC 7SD686 : All versions < V 4.05; SIPROTEC 7SJ66 : All versions < V 4.30. Attackers with network access to the device's web interface (port 80/tcp) could possibly circumvent authentication and perform certain administrative operations. A legitimate user must be logged into the web interface for the attack to be successful.
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 confidenceAuthentication bypass vulnerability in EN100 Ethernet module web interface (port 80/tcp) and multiple SIPROTEC devices. Attackers with network access could circumvent authentication mechanisms when a legitimate user has an active session, allowing unauthorized administrative operations.
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= 4.28CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 EN100 Ethernet Module presenceReview network inventory or scan for devices responding on port 80/tcp with EN100 HTTP service. Check device documentation or network diagrams for EN100 module deployment.Affected if EN100 Ethernet Module is deployed in the environment on port 80/tcp
-
Determine EN100 firmware versionAccess the EN100 web interface (port 80/tcp) and navigate to the firmware/version information page, or use SNMP queries if configured, to retrieve the installed firmware version.Affected if Firmware version is exactly 4.28 (only this exact version is affected)
-
Check for active web interface accessibilityVerify port 80/tcp is open and accessible on EN100 modules by attempting a TCP connection or reviewing firewall/segmentation rules that allow HTTP traffic to the module.Affected if Web interface on port 80/tcp is exposed to network (attackers need network access to exploit)
-
Identify affected SIPROTEC devicesReview asset inventory for SIPROTEC devices (e.g., SIPROTEC 4, SIPROTEC 7UT75, SIPROTEC 7UT612) and check their firmware versions against vendor advisories for this CVE.Affected if SIPROTEC devices with vulnerable firmware versions are present and have web interface enabled
Environment is affected if EN100 Ethernet Module with firmware version 4.28 is deployed with web interface (port 80/tcp) accessible on the network, or if vulnerable SIPROTEC devices with web interface enabled are present.
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 firmware to patched versions (EN100: V1.04.01/PROFINET, V1.11.00/Modbus, V1.03/DNP3, V1.21/IEC104; SIPROTEC devices to specified versions). If immediate patching is infeasible, restrict network access to the web interface using network segmentation or firewall rules.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7114 — 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-2016-7114 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