CVE-2018-5788
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 a Remote, Unauthenticated Denial of Service in the RIM (Radio Interface Module) process running 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 denial of service vulnerability exists in the Radio Interface Module (RIM) process of ExtremeWireless WiNG access points. Attackers can send crafted packets to the WiNG AP to crash the RIM process, causing service disruption. The vulnerability affects WiNG 5.x versions before 5.8.6.9 and 5.9.x versions before 5.9.1.3.
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.5.6, < 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/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.
-
Identify the device model and software platformAccess the AP CLI or management interface and run 'show version' or check the device information page to confirm the device is an ExtremeWireless WiNG access point and not a different platform.Affected if The device is not running ExtremeWireless WiNG firmware (e.g., it runs ExtremeXOS, Aerohive, or other platforms).
-
Determine the installed WiNG versionRun the command 'show version' in the AP CLI or check the management interface. Look for the WiNG version number displayed in the output.Affected if The version cannot be determined or is not visible in the output.
-
Compare the version against affected rangesReview the version number obtained from the previous step. Check if it falls within: 5.5.6 <= version < 5.8.6.9, OR 5.9.0 <= version < 5.9.1.3.Affected if The installed version is 5.5.6 through 5.8.6.8 (inclusive), or 5.9.0 through 5.9.1.2 (inclusive).
-
Verify the RIM process is activeRun 'show process' or 'show process RIM' in the CLI to confirm the Radio Interface Module process is running on the access point.Affected if The RIM process is running (this is the default state; the vulnerability affects devices where RIM is active).
The environment is affected if the access point runs ExtremeWireless WiNG firmware versions 5.5.6 through 5.8.6.8 or 5.9.0 through 5.9.1.2, with the RIM process active.
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
Apply the vendor-supplied patches (WiNG 5.8.6.9 or 5.9.1.3 and later) to all affected access points. If immediate patching is not feasible, isolate affected APs from untrusted networks to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5788 — 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-5788 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