CVE-2016-7112
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. Attackers with network access to the device's web interface (port 80/tcp) could possibly circumvent authentication and perform certain administrative operations.
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 confidenceAuthentication bypass vulnerability in the web interface (port 80/tcp) of Siemens EN100 Ethernet modules across multiple firmware variants (PROFINET IO, Modbus TCP, DNP3 TCP, IEC 104) and SIPROTEC Merging Unit 6MU80. Attackers with network access can circumvent authentication to perform 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 or 6MU80 devices on the networkScan the network for devices exposing HTTP on port 80/tcp. Use a tool like nmap or perform a web inventory scan. Look for HTTP services that respond with Siemens EN100 or SIPROTEC web interface banners.Affected if Devices with EN100 Ethernet modules or 6MU80 units are found listening on port 80/tcp.
-
Confirm web interface is accessibleAttempt to access the HTTP service on port 80 of identified devices. Navigate to the login page or device status page.Affected if The web interface is reachable and does not require authentication to access at least some pages.
-
Check firmware versionLog into the web interface (if authentication is working) or check device status/about pages. Look for firmware version information typically displayed in system info, device status, or about sections. Note the exact version number.Affected if The firmware version is 4.28 or lower, or displays as any version <= 4.28.
-
Verify device variant is affectedIdentify the specific EN100 variant (PROFINET IO, Modbus TCP, DNP3 TCP, or IEC 104) from the web interface or device labeling. Also check if the device is a SIPROTEC Merging Unit 6MU80.Affected if The device is an EN100 module (any variant) or 6MU80 with firmware <= 4.28.
A defender is affected if their network contains Siemens EN100 Ethernet modules or 6MU80 devices with accessible web interfaces running firmware version 4.28 or lower.
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.
dbcve · scopedUpdate firmware to patched versions (PROFINET IO V1.04.01+, Modbus TCP V1.11.00+, DNP3 TCP V1.03+, IEC 104 V1.21+, 6MU80 1.02.02+). If patching is not immediately feasible, restrict network access to the web interface.
Upgrade to: PROFINET IO >= V1.04.01, Modbus TCP >= V1.11.00, DNP3 TCP >= V1.03, IEC 104 >= V1.21, SIPROTEC 6MU80 >= 1.02.02
- Identify the specific EN100 Ethernet Module firmware variant (PROFINET IO, Modbus TCP, DNP3 TCP, or IEC 104) and confirm the current installed version
- For EN100 modules in SIPROTEC Merging Unit 6MU80, identify the firmware version
- Download the appropriate firmware update from Siemens support portal (www.siemens.com) or contact Siemens customer support
- Upgrade PROFINET IO variant to version V1.04.01 or later
- Upgrade Modbus TCP variant to version V1.11.00 or later
- Upgrade DNP3 TCP variant to version V1.03 or later
- Upgrade IEC 104 variant to version V1.21 or later
- Upgrade SIPROTEC 6MU80 EN100 module to version 1.02.02 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7112 — 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-7112 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