dbcve.org
Iologik E1200 Series FirmwareOperating system · Moxa

CVE-2016-8372

HIGH · 8.1 CVSS v3.1 Published 2017-02-13
Fix available
A fix is available. Upgrade to after 3.13 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in Moxa ioLogik E1210, firmware Version V2.4 and prior, ioLogik E1211, firmware Version V2.3 and prior, ioLogik E1212, firmware Version V2.4 and prior, ioLogik E1213, firmware Version V2.5 and prior, ioLogik E1214, firmware Version V2.4 and prior, ioLogik E1240, firmware Version V2.3 and prior, ioLogik E1241, firmware Version V2.4 and prior, ioLogik E1242, firmware Version V2.4 and prior, ioLogik E1260, firmware Version V2.4 and prior, ioLogik E1262, firmware Version V2.4 and prior, ioLogik E2210, firmware versions prior to V3.13, ioLogik E2212, firmware versions prior to V3.14, ioLogik E2214, firmware versions prior to V3.12, ioLogik E2240, firmware versions prior to V3.12, ioLogik E2242, firmware versions prior to V3.12, ioLogik E2260, firmware versions prior to V3.13, and ioLogik E2262, firmware versions prior to V3.12. A password is transmitted in a format that is not sufficiently secure.

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 confidence

The Moxa ioLogik series of industrial Ethernet controllers transmit user passwords in an insecure format (likely cleartext or weakly encoded), allowing network eavesdropping or man-in-the-middle attackers to capture valid credentials. This affects multiple E-series models across various firmware versions.

MitigationContact Moxa for patched firmware and apply available updates; until then, restrict network access to these devices and avoid transmitting credentials over untrusted networks.

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
Iologik E1200 Series FirmwareOperating system
Affected:<= 2.4<= 2.3<= 2.5
Iologik E2200 Series FirmwareOperating system
Affected:<= 3.11<= 3.12<= 3.13

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the ioLogik device model
    Locate the device physically or check the web administration interface for the model number. Look for 'E1200' or 'E2200' series identifiers on the device label or in the device status page.
    Affected if The device is a Moxa ioLogik E1200 or E2200 series controller.
  2. Determine the installed firmware version
    Access the device web interface and navigate to the System Settings or Firmware Information page. Record the firmware version number displayed.
    Affected if The firmware version is E1200 series <= 2.4, <= 2.3, or <= 2.5; OR E2200 series <= 3.11, <= 3.12, or <= 3.13.
  3. Verify network accessibility of the device
    Confirm the device has an active network IP address and is reachable on the local network or across network segments where authentication traffic could be intercepted.
    Affected if The device is network-accessible and can be reached by potential eavesdroppers or man-in-the-middle attackers.
  4. Confirm remote authentication is in use
    Check if the device web interface or administrative access is enabled and requires user credentials for login. Observe whether HTTPS is not enforced for the login process.
    Affected if User authentication is required and performed over the network without proper encryption.

A user is affected if they have an ioLogik E1200 or E2200 device with firmware in the specified version ranges and the device is accessible over a network where authentication traffic could be intercepted.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.13
Interim mitigation

Contact Moxa for patched firmware and apply available updates; until then, restrict network access to these devices and avoid transmitting credentials over untrusted networks.

Fix this in Iologik E1200 Series Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing4.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,960
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,336.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-8372 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-8372 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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