Security readout for executives and security teams
Plain-English summary
CVE-2017-13292 is an Android kernel issue where a bad bounds check could let a remote attacker trigger memory corruption. The CVE says exploitation needs no user interaction and no extra privileges. That makes unpatched Android kernel builds potentially serious, but the provided sources do not include CVSS, affected device models, or active exploitation evidence.
Executive priority
Treat as high priority for legacy Android fleets because the stated impact is remote code execution in kernel context without user interaction. Priority is lower for fully patched or retired devices, and evidence does not support claiming active exploitation.
Technical view
The flaw is an out-of-bounds write in wl_get_assoc_ies in wl_cfg80211.c, tied to Android ID A-70722061. The published impact is possible remote code execution in the Android kernel. The source bundle identifies Android kernel as affected, but does not provide CVSS, CWE, exploit details, or model-specific exposure.
Likely exposure
Exposure is limited to Android devices running affected Android kernel builds. Actual risk depends on OEM kernel contents and whether the April 2018 Android security bulletin fix was integrated into the device firmware.
Exploitation context
The CVE states remote code execution is possible without user interaction or additional privileges. The provided sources do not show CISA KEV listing, active exploitation, public exploit availability, or exploitation prerequisites beyond the CVE description.
Researcher notes
The source evidence is sparse. Focus validation on kernel lineage, vendor firmware status, and Android bulletin integration. Avoid assuming all Android devices are vulnerable; the bundle only names Android kernel and the affected wl_cfg80211.c function.
Mitigation direction
- Apply Android security updates that include the April 2018 bulletin fixes.
- Check OEM or carrier advisories for device-specific patch availability.
- Retire or isolate Android devices that cannot receive fixed firmware.
- Track Android ID A-70722061 in vulnerability management records.
Validation and detection
- Inventory Android devices and record OS build, kernel, and security patch level.
- Confirm whether April 2018 Android security bulletin fixes are present.
- Map vulnerable assets to business owners and network exposure.
- Review OEM release notes for CVE-2017-13292 or A-70722061 coverage.
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-13292 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/2018-04-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.