CVE-2017-0938
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 · uneditedDenial of Service attack in airMAX < 8.3.2 , airMAX < 6.0.7 and EdgeMAX < 1.9.7 allow attackers to use the Discovery Protocol in amplification attacks.
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 Discovery Protocol in Ubiquiti airMAX and EdgeMAX devices can be abused as a DDoS amplification vector. Attackers send small requests to vulnerable devices which broadcast Discovery packets, causing significantly larger responses that can be reflected at victims with spoofed source IPs, enabling high-bandwidth DoS attacks against third parties.
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< 6.0.7>= 6.0.7, < 8.3.2< 1.9.7CVSS 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.1/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 device firmware versionAccess the device's web interface or CLI and locate the firmware version information. For airMAX devices, check under the System or Status section. For EdgeMAX, run 'show version' or check the Device Dashboard.Affected if The firmware version is Ui Airos < 6.0.7, >= 6.0.7 and < 8.3.2, or EdgeMAX < 1.9.7
-
Verify Discovery Protocol is enabledCheck the device configuration for Discovery Protocol settings. For airMAX, look under System or Network settings for 'Discovery' or 'Enable Discovery'. For EdgeMAX, check configuration under system or interfaces for discovery-related settings. The protocol uses UDP port 10001.Affected if Discovery Protocol is enabled and operational on the device
-
Check network exposure of discovery portFrom an external network perspective, determine if UDP port 10001 is accessible on the device. This can be tested with an nmap scan from outside your perimeter: 'nmap -sU -p 10001 <device-ip>'. Also review firewall rules at network boundaries to see if inbound UDP port 10001 traffic is permitted.Affected if UDP port 10001 on the device is reachable from untrusted or external networks (the internet or otherwise unprotected segments)
The device is affected if it runs a vulnerable firmware version (airMAX < 6.0.7 or < 8.3.2, EdgeMAX < 1.9.7) AND has Discovery Protocol enabled AND is accessible from networks where attackers could send spoofed requests.
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 data1.9.76.0.78.3.2
Upgrade to airMAX 8.3.2/6.0.7 or EdgeMAX 1.9.7 or later. At network boundaries, filter or block inbound Discovery Protocol traffic (UDP port 10001 or similar) to prevent abuse of devices as reflectors.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0938 — 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-2017-0938 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