Security readout for executives and security teams
Plain-English summary
Affected Qualcomm-based Android/CAF devices may disclose Wi-Fi capability details while scanning for networks. The issue is primarily a privacy risk: someone nearby who can monitor wireless probe requests may learn device capability metadata before the phone connects.
Executive priority
Treat this as a legacy mobile privacy cleanup item, not an emergency. Prioritize if the organization still permits old Qualcomm-based Android devices in executive, regulated, or sensitive physical environments.
Technical view
The CVE describes probe requests from Android for MSM, Firefox OS for MSM, QRD Android, and CAF Linux-kernel Android releases exposing information elements that specify supported Wi-Fi features. The stated remediation direction is controlling those information elements through an ini file.
Likely exposure
Exposure is most relevant for legacy Qualcomm/CAF-based mobile builds from the 2017 era. Organizations with managed Android fleets should focus on older, unsupported, or OEM-customized devices that may not have received the relevant Android/Pixel or Qualcomm-aligned update.
Exploitation context
No provided source states active exploitation, and the CVE is not in KEV. Abuse appears to require local wireless proximity and passive observation of probe requests, producing privacy metadata rather than direct code execution or data compromise.
Researcher notes
The public record lacks CVSS, CWE, detailed patch identifiers, and exploit evidence. The core issue is excessive Wi-Fi capability disclosure in probe request information elements. Avoid assuming broader tracking impact beyond the privacy leakage described by the sources.
Mitigation direction
- Apply relevant OEM, Android, Pixel, or Qualcomm security updates where available.
- Review vendor guidance for ini-based control of Wi-Fi probe request information elements.
- Retire or restrict unsupported legacy Qualcomm/CAF Android devices.
- Use mobile device management to enforce minimum Android security patch levels.
Validation and detection
- Inventory devices using Qualcomm Android for MSM, QRD Android, or CAF-based kernels.
- Confirm affected devices received the relevant November 2017 security bulletin fixes or OEM equivalents.
- Check vendor configuration for probe request information-element controls.
- Prioritize validation on legacy devices still used in sensitive locations.
Public sources used
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.
CVE-2017-11022 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://source.android.com/security/bulletin/pixel/2017-11-01CVE reference · x_refsource_CONFIRM
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.