Security readout for executives and security teams
Plain-English summary
This CVE is an Android information disclosure issue in the media framework component libhevc. The bundle identifies Android 6.0 through 8.1 as affected, but provides no CVSS score, CWE, or exploit details. Treat it as a legacy mobile exposure requiring inventory and patch confirmation.
Executive priority
Prioritize as a legacy mobile hygiene issue unless affected devices remain in production. Business urgency rises for unmanaged, unsupported, or sensitive-use Android devices where patch status is unknown.
Technical view
CVE-2017-13297 maps to Android ID A-71766721 and affects Android 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, and 8.1. The vulnerable component is libhevc in Android media framework. The source bundle does not describe trigger conditions, impacted privileges, or disclosed data scope.
Likely exposure
Exposure is likely limited to Android devices running affected versions without the relevant vendor security update. The source bundle names Android broadly and links the April 2018 Pixel security bulletin, but does not enumerate device models beyond the affected Android versions.
Exploitation context
There is no KEV listing and no cited source in the bundle claims active exploitation. The public bundle does not provide exploit maturity, attack vector, or proof-of-concept status, so exploitation risk cannot be reliably ranked from these sources alone.
Researcher notes
The source bundle is sparse: no CVSS, CWE, attack vector, patch commit, or exploit discussion is provided. Analysis should stay anchored to Android ID A-71766721, libhevc, affected versions, and the April 2018 Pixel bulletin reference.
Mitigation direction
- Apply vendor security updates that include the April 2018 Android or Pixel bulletin fixes.
- Move affected Android 6.0 through 8.1 devices to supported patched releases where possible.
- Check OEM guidance for devices that do not receive Pixel or Android bulletin updates.
- Retire or isolate unsupported devices that cannot receive relevant security fixes.
Validation and detection
- Inventory Android devices by OS version and security patch level.
- Identify devices running Android 6.0 through 8.1.
- Confirm whether each device received the relevant April 2018 vendor security update.
- Review MDM records for unsupported or stale Android builds.
- Track exceptions where OEM patch applicability cannot be confirmed.
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-13297 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/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.