Security readout for executives and security teams
Plain-English summary
This Android flaw could let a local attacker bypass a permission check and start an activity with system privileges. It affects Android 6.0 through 8.1 as listed in the CVE source. The bundle does not provide CVSS, exploit maturity, or detailed patch mechanics.
Executive priority
Treat this as high priority for legacy Android fleets because the stated impact is local elevation to system privileges without user interaction. Urgency depends on whether affected versions remain in production and whether vendor patches are available for those devices.
Technical view
CVE-2017-13289 is a permission bypass in RttManager.java involving writeToParcel and createFromParcel write-size mismatch handling. The stated impact is local escalation of privileges to system-level activity launch. No user interaction or additional execution privileges are required, according to the CVE description.
Likely exposure
Exposure is most likely on Android 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, or 8.1 devices that have not received the relevant Android security bulletin fixes.
Exploitation context
The source bundle describes local privilege escalation only. It does not cite active exploitation, public exploit availability, or remote attack capability. CISA KEV is false in the provided data, so active exploitation should not be claimed.
Researcher notes
The available evidence identifies the vulnerable component, affected Android versions, impact class, and Android bug ID A-70398564. It does not include CVSS, CWE mapping, proof-of-concept status, or implementation-level remediation detail.
Mitigation direction
- Review Google’s April 2018 Android Security Bulletin for vendor fix guidance.
- Update affected Android devices to a security patch level covering this bulletin.
- Prioritize managed or shared Android devices running listed affected versions.
- Retire or isolate devices that cannot receive vendor security updates.
Validation and detection
- Inventory Android OS versions and security patch levels across managed devices.
- Identify devices running Android 6.0 through 8.1 without relevant fixes.
- Check OEM update status against Google’s April 2018 bulletin guidance.
- Confirm remediation through MDM reporting or device settings evidence.
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-13289 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.