Security readout for executives and security teams
Plain-English summary
CVE-2017-13290 is an Android information disclosure flaw. A missing bounds check could let a local attacker read data they should not access. The public record says no extra execution privileges or user interaction are needed, but it does not show active exploitation.
Executive priority
Treat this as a legacy-device hygiene issue. It is not supported as actively exploited in the supplied sources, but unpatched Android 6.0 through 8.1 devices may expose sensitive local information and should be updated or removed from trusted use.
Technical view
The flaw is an out-of-bounds read in sdp_server_handle_client_req in sdp_server.cc. The affected Android versions listed are 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, and 8.1. Impact is local information disclosure.
Likely exposure
Exposure is most likely on legacy Android devices still running the listed versions or devices without relevant Android security bulletin updates. Current, vendor-supported Android devices are less likely to remain exposed if security patches were applied.
Exploitation context
The CVE record describes local exploitation with no additional execution privileges and no user interaction. The supplied sources do not identify public exploit code, exploitation in the wild, or CISA KEV listing.
Researcher notes
Evidence is limited to the CVE description and Android bulletin reference. No CVSS, CWE, exploit status, or detailed fix text is supplied. Avoid expanding affected scope beyond Android versions explicitly listed in the record.
Mitigation direction
- Review the Android April 2018 security bulletin and device vendor guidance.
- Apply available Android security updates for affected device versions.
- Inventory Android 6.0 through 8.1 devices across managed and unmanaged fleets.
- Retire, replace, or restrict devices that cannot receive relevant updates.
Validation and detection
- Confirm device Android versions and security patch levels.
- Check whether affected versions remain in mobile device management inventory.
- Verify vendor advisories for each device model against the Android bulletin.
- Prioritize validation on devices handling sensitive business or customer data.
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-13290 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.
