dbcve.org
Mb3170 FirmwareOperating system · Moxa

CVE-2019-9099

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. A Buffer overflow in the built-in web server allows remote attackers to initiate DoS, and probably to execute arbitrary code (issue 1 of 2).

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

A buffer overflow vulnerability exists in the built-in web server of Moxa MGate MB3170, MB3270, MB3280, MB3480, MB3660, and MB3180 industrial protocol gateways. The overflow allows remote unauthenticated attackers to cause denial of service and potentially execute arbitrary code on affected devices.

MitigationApply the vendor-supplied firmware updates: MB3170/MB3270 to version 4.1 or later, MB3280/MB3480 to version 3.1 or later, MB3660 to version 2.3 or later, and MB3180 to version 2.1 or later. If patching is not immediately possible, restrict network access to the web server interface via firewall or access controls.

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 device model
    Check the device label on the physical unit or access the web interface and look for the model number displayed on the login page or system status page
    Affected if The device is not one of the following models: MB3170, MB3270, MB3180, MB3280, MB3480, or MB3660
  2. Check the firmware version via web interface
    Log into the device web interface and navigate to System > Firmware Version or System > Status to view the installed firmware version
    Affected if The firmware version matches or is lower than: MB3170/MB3270 <= 4.0, MB3180 <= 2.0, MB3280/MB3480 <= 3.0, MB3660 <= 2.2
  3. Check firmware version via console or serial connection
    Connect to the device console or serial port, log in, and run the firmware version command (typically 'show sysinfo' or 'version' depending on the CLI)
    Affected if The firmware version matches or is lower than the affected versions listed above
  4. Verify the built-in web server is accessible
    Attempt to access the device web interface by navigating to the device IP address on ports 80 or 443
    Affected if The web interface is reachable from the network, as the buffer overflow vulnerability exists in the built-in web server component

The device is affected if it is an MGate MB3170, MB3270, MB3180, MB3280, MB3480, or MB3660 with firmware version at or below the affected thresholds and the web server interface is accessible on 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

Apply the vendor-supplied firmware updates: MB3170/MB3270 to version 4.1 or later, MB3280/MB3480 to version 3.1 or later, MB3660 to version 2.3 or later, and MB3180 to version 2.1 or later. If patching is not immediately possible, restrict network access to the web server interface via firewall or access controls.

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 exact model number (MB3170, MB3270, MB3180, MB3280, MB3480, or MB3660) of the affected Moxa MGate device
  2. 2. Check the current firmware version on the device through the web interface or console
  3. 3. Download the appropriate firmware update from the official Moxa website (www.moxa.com)
  4. 4. Review the firmware release notes for any special upgrade instructions or prerequisites
  5. 5. Back up the device configuration before performing the firmware upgrade
  6. 6. Upload and install the firmware through the device's web interface or management tool
  7. 7. Verify the firmware version after upgrade to confirm the fix was applied
  8. 8. Test that the device functionality remains operational after the update
Caveat Review Moxa release notes for compatibility; some legacy configurations may need adjustment after upgrade

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

Fix this in Mb3170 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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