CVE-2018-5787
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 Stack Overflow 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 confidenceStack-based buffer overflow in the RIM (Radio Interface Module) process of ExtremeWireless WiNG access points allows remote, unauthenticated attackers to execute arbitrary code via crafted network packets. The vulnerability affects WiNG 5.x versions before 5.8.6.9 and 5.9.x 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.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
- 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 WiNG firmware versionAccess the access point CLI or web interface and run 'show version' or check the firmware version displayed in the system information pageAffected if The displayed version is 5.x before 5.8.6.9, or 5.9.x before 5.9.1.3, or any version >= 5.0 and < 5.8.6.9, or >= 5.9.0 and < 5.9.1.3
-
Confirm the RIM process is activeIn the CLI, run 'show process' or 'show rim status' to verify the Radio Interface Module process is running on the deviceAffected if The RIM process is listed as running or active (the vulnerability exists in this process)
-
Determine network accessibility of the RIM serviceCheck firewall rules or ACLs on the access point using 'show firewall' or 'show ip interface' to see if the RIM service (typically UDP/port 2457 or similar management ports) is exposed to untrusted networksAffected if The RIM service port is open to unauthenticated network access from outside the trusted management network
Your environment is affected if the installed WiNG firmware version falls within 5.0 to less than 5.8.6.9, or 5.9.0 to less than 5.9.1.3, AND the RIM process is running and accessible to unauthenticated network 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 data5.8.6.95.9.1.3
Upgrade ExtremeWireless WiNG firmware to version 5.8.6.9, 5.9.1.3, or later. If patching is not immediately possible, restrict network access to the RIM service using firewall rules or network segmentation.
- 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-5787 — 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-5787 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