CVE-2019-9101
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 · uneditedAn 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. Sensitive information is sent to the web server in cleartext, which may allow an attacker to discover the credentials if they are able to observe traffic between the web browser and the server.
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 serial-to-Ethernet gateways (MB3170, MB3270, MB3280, MB3480, MB3660, MB3180) transmit user credentials in cleartext over HTTP to the web management interface, allowing remote attackers on the same network segment to intercept authentication credentials via packet sniffing or man-in-the-middle attacks.
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.0<= 4.0<= 2.0<= 3.0<= 3.0<= 2.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 the MGate device modelAccess the web management interface and look for the model number in the header or system status page, or check the physical device labelAffected if The device is not one of MB3170, MB3270, MB3280, MB3480, MB3660, or MB3180 (those models are not affected)
-
Check the installed firmware versionLog into the web interface and navigate to System Settings > Firmware Update or System Information to view the current firmware versionAffected if The firmware version is at or below 4.0 for MB3170/MB3270, 2.0 for MB3180, 3.0 for MB3280/MB3480, or 2.2 for MB3660
-
Verify if HTTP is enabled for the web interfaceAttempt to access the device via HTTP (port 80). Check the web server configuration or connection settings to see if HTTP access is permittedAffected if HTTP (not HTTPS) access to the management interface is enabled and functional
-
Confirm cleartext credential transmissionUse a network packet capture tool on the same network segment while authenticating to the web interface. Observe if the login request contains username and password in plain textAffected if Authentication packets contain readable credentials rather than being encrypted
You are affected if you have an MGate MB3170/3270/3180/3280/3480/3660 device running the vulnerable firmware version AND the HTTP web management interface is accessible, allowing credentials to be intercepted in cleartext.
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 dataUpgrade to the patched firmware versions (4.1 for MB3170/MB3270, 3.1 for MB3280/MB3480, 2.3 for MB3660, 2.1 for MB3180). If immediate upgrade is not feasible, restrict network access to the management interface via VLAN segmentation or firewall rules.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9101 — 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-2019-9101 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