CVE-2018-5790
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 in Extreme Networks ExtremeWireless WiNG 5.x before 5.8.6.9 and 5.9.x before 5.9.1.3. There is Remote, Unauthenticated "Global" Denial of Service in the RIM (Radio Interface Module) over the MINT (Media Independent Tunnel) Protocol on the WiNG Access Point via crafted packets.
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 confidenceA remote, unauthenticated attacker can send specially crafted packets to the MINT (Media Independent Tunnel) protocol on affected ExtremeWireless WiNG Access Points, causing a denial of service in the Radio Interface Module (RIM). This 'Global' DoS renders the entire access point non-functional.
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>= 5.0, < 5.8.6.9>= 5.9.0, < 5.9.1.3CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/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.
-
Confirm device modelIdentify the access point model via CLI command 'show version' or through the management interface. Look for ExtremeWireless WiNG AP models such as AP7602, AP7621, AP7632, AP7662, AP8163, AP8543, AP8565, AP8635, AP8645, or similar WiNG-series access points.Affected if Device is not an ExtremeWireless WiNG Access Point
-
Check installed firmware versionExecute 'show version' in the AP CLI or check via management interface to retrieve the current WiNG firmware version number.Affected if Cannot determine the firmware version
-
Compare version against affected rangesCompare your installed version against: 5.0 through 5.8.6.8 (vulnerable), or 5.9.0 through 5.9.1.2 (vulnerable). Versions 5.8.6.9 and above (5.x branch) or 5.9.1.3 and above (5.9.x branch) are not affected.Affected if Installed version is 5.0 to 5.8.6.8, or 5.9.0 to 5.9.1.2
-
Verify MINT protocol statusCheck if MINT protocol is enabled via CLI command 'show mint' or through the wireless controller configuration. MINT is the attack vector for this vulnerability.Affected if MINT protocol is enabled on the device
-
Assess network exposureDetermine if the MINT service port (UDP 2436) is exposed to untrusted networks. Check firewall rules and network segmentation that may limit external access to the AP management interface.Affected if MINT port is accessible from untrusted network segments
Device is affected if it is an ExtremeWireless WiNG AP running firmware version 5.0-5.8.6.8 or 5.9.0-5.9.1.2 AND has MINT protocol enabled and accessible from the network.
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 data5.8.6.95.9.1.3
Upgrade ExtremeWireless WiNG firmware to version 5.8.6.9 or later (5.x branch) or 5.9.1.3 or later (5.9.x branch) to remediate this vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5790 — 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-2018-5790 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