Security readout for executives and security teams
Plain-English summary
CVE-2017-13275 is an Android flaw that can expose local information when a user interacts with specially handled content. The source identifies Android 8.0 and 8.1 as affected. No active exploitation is reported in the provided sources, and it is not listed as KEV.
Executive priority
Treat this as a moderate legacy Android exposure. It is not an emergency based on the provided evidence, but unpatched Android 8.0 or 8.1 devices should be identified and remediated through normal vulnerability management.
Technical view
The issue is an out-of-bounds read in getVSCoverage of CmapCoverage.cpp caused by an incorrect bounds check. The stated impact is local information disclosure with no additional privileges required. User interaction is required. The provided sources do not include CVSS, CWE, exploit details, or detailed remediation mechanics.
Likely exposure
Exposure is most likely limited to Android 8.0 and 8.1 devices that have not received the relevant April 2018 Android security update or equivalent OEM patch.
Exploitation context
The provided sources describe user interaction as required and local information disclosure as the impact. They do not show public exploitation, KEV listing, exploit availability, or remote unauthenticated compromise.
Researcher notes
Evidence is limited to the CVE description and Android bulletin reference. The root cause is bounds-check failure in CmapCoverage.cpp, producing an out-of-bounds read. No CVSS, CWE, proof-of-concept, or exploitation evidence is provided in the source bundle.
Mitigation direction
- Review the Android April 2018 security bulletin for vendor guidance.
- Apply relevant Android or OEM security updates to affected devices.
- Prioritize unsupported Android 8.0 and 8.1 devices for replacement or isolation.
- Restrict handling of untrusted content on unpatched affected devices.
Validation and detection
- Inventory Android devices running versions 8.0 and 8.1.
- Check whether devices received the relevant April 2018 Android security update.
- Review OEM patch notes for CVE-2017-13275 coverage.
- Confirm unsupported affected devices are removed, replaced, or risk-accepted.
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-13275 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.