CVE-2016-5804
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 · uneditedMoxa MGate MB3180 before 1.8, MGate MB3280 before 2.7, MGate MB3480 before 2.6, MGate MB3170 before 2.5, and MGate MB3270 before 2.7 use weak encryption, which allows remote attackers to bypass authentication via a brute-force series of guesses for a parameter value.
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 Moxa MGate series protocol gateways (MB3180, MB3280, MB3480, MB3170, MB3270) use weak encryption for authentication, allowing remote attackers to bypass authentication via brute-force attacks on an encryption parameter value.
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< 1.8< 2.7< 2.6< 2.5< 2.7CVSS 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.1/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 the MGate modelAccess the device web interface, console, or check the device label to confirm the exact model number (MB3180, MB3280, MB3480, MB3170, or MB3270).Affected if The model is one of the five affected products listed.
-
Retrieve the current firmware versionLog into the MGate web interface and navigate to the System Settings or Status page to view the firmware version. Alternatively, use the console/Telnet interface and run the 'show system' or 'version' command.Affected if The firmware version cannot be retrieved or shows an unlisted version.
-
Compare firmware version against the thresholdFor MB3180, check if version is below 1.8. For MB3280, check if below 2.7. For MB3480, check if below 2.6. For MB3170, check if below 2.5. For MB3270, check if below 2.7.Affected if The installed firmware version falls below the threshold for your specific model.
-
Verify remote management accessConfirm whether the MGate management interface (web, Telnet, or SNMP) is exposed to untrusted networks or the internet.Affected if Remote management interfaces are accessible from untrusted networks and the firmware is below the fixed versions.
You are affected if you have an MGate MB3180, MB3280, MB3480, MB3170, or MB3270 running firmware below 1.8, 2.7, 2.6, 2.5, or 2.7 respectively, with remote management access enabled.
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 · scoped1.82.52.6
Upgrade the MGate firmware to version 1.8 (MB3180), 2.7 (MB3280), 2.6 (MB3480), 2.5 (MB3170), or 2.7 (MB3270) or later. Until patched, restrict network access to management interfaces using firewalls or VPNs.
Mgate MB3180: firmware 1.8 | Mgate MB3280: firmware 2.7 | Mgate MB3480: firmware 2.6 | Mgate MB3170: firmware 2.5 | Mgate MB3270: firmware 2.7
- Identify the exact model number of the Moxa MGate device (MB3180, MB3280, MB3480, MB3170, or MB3270)
- Visit the official Moxa support website (www.moxa.com) or contact Moxa technical support to obtain the firmware update
- Download the appropriate firmware version for your device model: MB3180 to version 1.8, MB3280 to version 2.7, MB3480 to version 2.6, MB3170 to version 2.5, or MB3270 to version 2.7
- Review the Moxa firmware upgrade instructions in the product manual
- Back up the current device configuration before proceeding with the upgrade
- Connect to the device via Ethernet and access the web-based management interface or console
- Upload and apply the firmware update following the manufacturer's documented procedure
- After upgrade, verify the firmware version has been successfully updated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5804 — 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-5804 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