CVE-2018-5794
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 No Authentication for the AeroScout Service via a crafted UDP packet.
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 AeroScout location tracking service in ExtremeWireless WiNG 5.x and 5.9.x lacks authentication requirements, allowing unauthenticated attackers to send crafted UDP packets to the service without any credentials.
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
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 ExtremeWireless WiNG installation and versionCheck the installed WiNG version by accessing the device CLI or management interface. Common commands: 'show version' or 'show system info' in the controller CLI. Alternatively, check the firmware file name or system dashboard for version information.Affected if Version is 5.0 through 5.8.6.8, or 5.9.0 through 5.9.1.2 (falls within >=5.0,<5.8.6.9 or >=5.9.0,<5.9.1.3)
-
Locate AeroScout service processCheck if the AeroScout location tracking service is running on the WiNG device. In the CLI, use 'show process' or 'show services' to list active services. Look for processes named 'aeroscout', 'LocationEngine', or similar location tracking services.Affected if AeroScout or location tracking service is listed as running or enabled
-
Identify AeroScout UDP port exposureCheck open UDP ports on the device. In CLI, use 'show ip interface' or port scanning tools to identify listening UDP ports. AeroScout typically uses UDP port 5500 for its location protocol.Affected if UDP port 5500 (or other AeroScout-specific ports) is open and listening
-
Verify network accessibility of the serviceConfirm whether the AeroScout UDP service is reachable from network segments outside the trusted management network. Check interface bindings and access control lists: 'show running-config' or 'show access-list' to see if UDP traffic to the AeroScout port is permitted from untrusted networks.Affected if UDP service is accessible from network segments beyond the local management network
If the device runs ExtremeWireless WiNG version 5.0-5.8.6.8 or 5.9.0-5.9.1.2 AND the AeroScout location tracking service is enabled with its UDP port exposed to the network, the environment is vulnerable to unauthenticated UDP packet injection.
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 to ExtremeWireless WiNG version 5.8.6.9 or 5.9.1.3 or later to patch the vulnerability. If immediate patching is not possible, consider network segmentation to restrict UDP access to the AeroScout service.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5794 — 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-5794 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