CVE-2019-9097
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 high rate of transit traffic may cause a low-memory condition and a denial of service.
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 confidenceThis is a denial-of-service vulnerability in Moxa MGate serial-to-Ethernet gateway devices (MB3170, MB3270, MB3280, MB3480, MB3660, MB3180). The devices enter a low-memory condition when exposed to high-rate transit traffic, causing them to become unresponsive. The vulnerability affects specific firmware versions before 4.1 (MB3170/MB3270), 3.1 (MB3280/MB3480), 2.3 (MB3660), and 2.1 (MB3180).
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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 device web interface, console, or management panel and locate the model number (MB3170, MB3270, MB3280, MB3480, MB3660, or MB3180).Affected if The device is one of these six models.
-
Check the installed firmware versionLocate the firmware version information in the device web interface under 'System Settings' or 'Device Status', or via console command 'show system info' or equivalent. Compare the version number against the affected ranges.Affected if Firmware version is <= 4.0 on MB3170/MB3270, <= 3.0 on MB3280/MB3480, <= 2.2 on MB3660, or <= 2.0 on MB3180.
-
Verify network exposure to transit trafficReview the device network configuration and adjacent network devices to determine if the MGate device is receiving high-rate transit traffic from external or untrusted networks.Affected if The device is directly exposed to high-rate transit traffic from network segments with uncontrolled traffic volume.
-
Check for device responsivenessAttempt to access the device web interface, ping the device, or send a management query. Observe whether the device becomes unresponsive or exhibits significantly delayed responses.Affected if The device is unresponsive, extremely slow to respond, or fails to respond to management queries.
A user is affected if they have an MGate MB3170, MB3270, MB3280, MB3480, MB3660, or MB3180 device running firmware at or below the affected version thresholds AND the device is exposed to high-rate transit traffic.
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 affected devices to the latest patched firmware versions (4.1+, 3.1+, 2.3+, 2.1+ respectively). If immediate patching is not possible, implement network rate limiting or traffic filtering on adjacent network devices to reduce transit traffic volume to affected gateways.
- 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-9097 — 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-9097 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