Security readout for executives and security teams
Plain-English summary
Certain airMAX and EdgeMAX devices could be abused through their Discovery Protocol to amplify denial-of-service traffic. The main business risk is operational disruption and possible participation in attacks against others if exposed devices remain unpatched.
Executive priority
Treat as a targeted network hygiene item. Prioritize exposed wireless or routing infrastructure because compromised availability or amplification abuse can affect business operations and reputation.
Technical view
CVE-2017-0938 is a CWE-400 resource consumption issue affecting airMAX versions before 8.3.2 and 6.0.7, and EdgeRouter/EdgeMAX versions before 1.9.7. The CVE states attackers can use the Discovery Protocol in amplification attacks. No CVSS score is provided in the bundle.
Likely exposure
Exposure is most likely where affected airMAX or EdgeMAX management or discovery services are reachable from untrusted networks. Internal-only deployments still matter if hostile traffic can reach the discovery protocol.
Exploitation context
The provided sources describe denial-of-service amplification potential but do not show active exploitation. The CVE is not listed as KEV in the supplied bundle, so active exploitation should not be assumed.
Researcher notes
Evidence is limited to CVE metadata, release references, and a HackerOne report link. The bundle does not provide CVSS, detailed protocol conditions, packet specifics, or confirmed exploitation, so validation should focus on versioning and exposure.
Mitigation direction
- Identify airMAX and EdgeMAX devices and record firmware versions.
- Upgrade airMAX to 6.0.7 or 8.3.2, as applicable.
- Upgrade EdgeRouter or EdgeMAX firmware to 1.9.7 or later.
- Restrict discovery protocol exposure to trusted management networks.
- Check current vendor guidance before production changes.
Validation and detection
- Confirm no affected firmware versions remain in asset inventory.
- Review firewall rules for discovery protocol exposure from untrusted networks.
- Validate device management interfaces are not internet-exposed unnecessarily.
- Check monitoring for unusual UDP amplification or denial-of-service traffic patterns.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2017-0938 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://community.ubnt.com/t5/airMAX-Updates-Blog/airOS-v6-0-7-Has-Been-Released/ba-p/2056522CVE reference · x_refsource_MISC
- https://hackerone.com/reports/221625CVE reference · x_refsource_MISC
- https://community.ubnt.com/t5/airMAX-Updates-Blog/airOS-v8-3-2-Has-Been-Released/ba-p/2049215CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.