CVE-2016-4785
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. The integrated web server (port 80/tcp) of the affected devices could allow remote attackers to obtain a limited amount of device memory content if network access was obtained. This vulnerability only affects EN100 Ethernet module included in SIPROTEC4 and SIPROTEC Compact devices.
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 confidenceThe EN100 Ethernet module's integrated web server (port 80/tcp) contains an information disclosure vulnerability allowing remote attackers with network access to read limited device memory content. This affects multiple firmware variants (PROFINET IO < V1.04.01, Modbus TCP < V1.11.00, DNP3 TCP < V1.03, IEC 104 < V1.21) in SIPROTEC4 and SIPROTEC Compact protection devices.
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.26all 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Identify SIPROTEC device and EN100 moduleConfirm the target device is a Siemens SIPROTEC4 or SIPROTEC Compact protection device with an EN100 Ethernet module. Check device documentation, inventory records, or network discovery for the EN100 module presence.Affected if Device is a SIPROTEC4 or SIPROTEC Compact with an EN100 Ethernet module installed
-
Verify web server is accessible on port 80Test TCP port 80 connectivity to the EN100 module's IP address using a network scan tool (such as netcat or nmap) or attempt an HTTP request. Confirm the integrated web server is responding.Affected if Port 80/tcp is open and the EN100 web server is accessible
-
Check PROFINET IO firmware versionAccess the EN100 module web interface or management console to retrieve the PROFINET IO firmware version. Compare the installed version against the affected range: versions below V1.04.01.Affected if PROFINET IO firmware version is below V1.04.01
-
Check Modbus TCP firmware versionAccess the EN100 module web interface or management console to retrieve the Modbus TCP firmware version. Compare the installed version against the affected range: versions below V1.11.00.Affected if Modbus TCP firmware version is below V1.11.00
-
Check DNP3 TCP firmware versionAccess the EN100 module web interface or management console to retrieve the DNP3 TCP firmware version. Compare the installed version against the affected range: versions below V1.03.Affected if DNP3 TCP firmware version is below V1.03
-
Check IEC 104 firmware versionAccess the EN100 module web interface or management console to retrieve the IEC 104 firmware version. Compare the installed version against the affected range: versions below V1.21.Affected if IEC 104 firmware version is below V1.21
The environment is affected if the EN100 module web server on port 80 is accessible and any of the installed protocol firmware variants (PROFINET IO, Modbus TCP, DNP3 TCP, or IEC 104) falls below its respective minimum version threshold.
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 affected EN100 Ethernet module firmware to the specified minimum versions; if updates are not feasible, restrict network access to port 80/tcp via firewall or network segmentation and disable the web server if not operationally required.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4785 — 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-4785 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