dbcve.org
Mb3170 FirmwareOperating system · Moxa

CVE-2019-9095

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-11
Fix available
A fix is available. Upgrade to after 4.0 or later.
See remediation →
100/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 on Moxa MGate MB3170 and MB3270 devices before 4.1, MB3280 and MB3480 devices before 3.1, MB3660 devices before 2.3, and MB3180 devices before 2.1. An attacker may be able to intercept weakly encrypted passwords and gain administrative access.

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

Moxa MGate industrial protocol gateways contain a vulnerability where password encryption is weak, allowing an attacker who can intercept network traffic to recover plaintext administrative credentials and gain full administrative access to the device.

MitigationUpdate firmware to versions 4.1 or higher for MB3170/MB3270, 3.1 or higher for MB3280/MB3480, 2.3 or higher for MB3660, and 2.1 or higher for MB3180. If patching is delayed, isolate affected devices on a restricted network segment.

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
Mb3170 FirmwareOperating system
Affected:<= 4.0
Mb3270 FirmwareOperating system
Affected:<= 4.0
Mb3180 FirmwareOperating system
Affected:<= 2.0
Mb3280 FirmwareOperating system
Affected:<= 3.0
Mb3480 FirmwareOperating system
Affected:<= 3.0
Mb3660 FirmwareOperating system
Affected:<= 2.2

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
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 checks

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

  1. Identify the MGate model number
    Check the device label, web interface header, or console output for the exact model (MB3170, MB3270, MB3180, MB3280, MB3480, or MB3660)
    Affected if The model is one of the six affected models listed in the CVE
  2. Locate the firmware version
    Access the device web interface and navigate to System Settings > Firmware Version, or use the console and run the 'show system' or 'version' command
    Affected if Unable to retrieve firmware version from the device
  3. Compare installed version against affected ranges
    For MB3170/MB3270: affected if <= 4.0. For MB3180: affected if <= 2.0. For MB3280/MB3480: affected if <= 3.0. For MB3660: affected if <= 2.2
    Affected if The installed firmware version falls at or below the threshold for your specific model
  4. Verify remote management is enabled
    Check via web interface under Network > HTTP/HTTPS or Console > Remote Management to confirm administrative access is exposed
    Affected if Remote management (web or console) is enabled and accessible over the network

You are affected if you have an MB3170, MB3270, MB3180, MB3280, MB3480, or MB3660 device running firmware at or below the version threshold for that model, with administrative interfaces exposed over the network.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.0
Interim mitigation

Update firmware to versions 4.1 or higher for MB3170/MB3270, 3.1 or higher for MB3280/MB3480, 2.3 or higher for MB3660, and 2.1 or higher for MB3180. If patching is delayed, isolate affected devices on a restricted network segment.

Recommended fix High confidence

MB3170/MB3270: firmware 4.1 | MB3280/MB3480: firmware 3.1 | MB3660: firmware 2.3 | MB3180: firmware 2.1

  1. 1. Identify the specific Moxa MGate model number (MB3170, MB3270, MB3180, MB3280, MB3480, or MB3660)
  2. 2. Check the current firmware version through the device's web interface or console
  3. 3. Download the appropriate fixed firmware version from Moxa's official support website: MB3170/MB3270 to version 4.1, MB3280/MB3480 to version 3.1, MB3660 to version 2.3, MB3180 to version 2.1
  4. 4. Follow Moxa's firmware upgrade instructions in the product manual to apply the update
  5. 5. After upgrade, verify the firmware version and change administrative passwords as a precautionary measure
Caveat Standard firmware upgrade - review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mb3170 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-9095 — 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-2019-9095 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