CVE-2019-9102
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. A predictable mechanism of generating tokens allows remote attackers to bypass the cross-site request forgery (CSRF) protection mechanism.
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 industrial gateways use a predictable mechanism to generate anti-CSRF tokens. Due to insufficient randomness or entropy in token generation, remote attackers can deduce or predict valid tokens, allowing them to craft malicious cross-site requests that bypass the CSRF protection and perform unauthorized actions on behalf of authenticated users.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 or check the device label/serial number to confirm the exact model (Mb3170, Mb3270, Mb3180, Mb3280, Mb3480, or Mb3660)Affected if The model is one of: Mb3170, Mb3270, Mb3180, Mb3280, Mb3480, or Mb3660
-
Check the firmware versionLog into the web management interface and navigate to System Settings > Firmware Version, or use the device's serial console to run the firmware version commandAffected 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 web interface accessibilityConfirm the device HTTP/HTTPS management interface is reachable from network segments that contain users or potential attackersAffected if The web interface is exposed to untrusted networks (LAN, DMZ, or internet-facing) and the firmware version matches the affected ranges above
-
Inspect CSRF token behaviorLog into the device, perform multiple actions (such as saving settings or changing configurations), and observe whether the anti-CSRF token follows a predictable pattern or remains constant across sessionsAffected if Tokens are reused, increment predictably, or remain static across different requests or sessions (indicating insufficient randomness)
The device is affected if it is an Mb3170, Mb3270, Mb3180, Mb3280, Mb3480, or Mb3660 model running firmware at or below the affected version limits and has its web interface accessible to potential attackers.
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 dataUpdate firmware to the patched versions (MB3170/MB3270: 4.1+, MB3280/MB3480: 3.1+, MB3660: 2.3+, MB3180: 2.1+). If immediate patching is not feasible, consider deploying additional CSRF defenses such as SameSite cookie attributes, custom request headers, or robust referer validation at the network perimeter.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9102 — 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-9102 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