Security readout for executives and security teams
Plain-English summary
CVE-2017-13267 is an Android flaw that can corrupt stack memory in a vendor command parser. Google described the impact as remote escalation of privilege without user interaction or additional privileges. Exposure is mainly older Android 6.0 through 8.1 devices that did not receive the April 2018 Android security fixes or equivalent OEM updates.
Executive priority
Treat this as a high-priority legacy Android exposure issue. The business risk is concentrated in old or unsupported devices, especially where device inventory and patch visibility are weak.
Technical view
The issue is a missing bounds check in avrc_pars_vendor_cmd in avrc_pars_tg.cc, causing possible stack corruption. The source bundle lists Android 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, and 8.1 as affected. No CVSS vector, CWE, proof-of-exploit, or detailed patch diff is provided in the bundle.
Likely exposure
Organizations may be exposed through unmanaged, embedded, kiosk, rugged, or legacy Android devices running versions 6.0 through 8.1 without the April 2018 Android security bulletin fixes or OEM equivalent patches.
Exploitation context
The source states exploitation could be remote, require no user interaction, and need no additional execution privileges. The bundle does not include KEV status, public exploitation evidence, exploit maturity, attack prerequisites, or affected deployment conditions beyond Android versions.
Researcher notes
Evidence is limited to the CVE description and Android April 2018 bulletin reference. Do not assume active exploitation, affected OEM models, or specific mitigations beyond applying vendor security updates unless confirmed by additional sources.
Mitigation direction
- Apply Android security updates from the April 2018 bulletin or OEM equivalent guidance.
- Inventory Android 6.0 through 8.1 devices and confirm security patch level.
- Retire or isolate unsupported devices that cannot receive vendor fixes.
- Check device vendor advisories for model-specific patch availability and timelines.
Validation and detection
- Identify devices running Android 6.0 through 8.1 in fleet management records.
- Verify each device has the April 2018 Android security patch level or later.
- Review OEM security bulletin mappings for equivalent patched firmware builds.
- Flag unsupported or unpatchable devices for replacement or compensating controls.
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-13267 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.