Security readout for executives and security teams
Plain-English summary
This is an Android local privilege escalation flaw. An attacker who can run an unprivileged process on an affected device may be able to gain higher privileges without user interaction. The available sources do not show remote exploitation or confirmed active exploitation.
Executive priority
Treat this as a high-priority mobile fleet hygiene issue for legacy Android devices. It is not evidenced as internet-remote or actively exploited, but successful local exploitation could compromise device confidentiality, integrity, and availability.
Technical view
The issue is an integer overflow in Android String16.cpp that can cause an out-of-bounds write. CVSS 3.1 is 8.4: local attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to Android 6, 6.0.1, 7, 7.1.1, 7.1.2, 8, and 8.1 builds lacking the relevant vendor security update. The bundle does not identify other affected products.
Exploitation context
The bundle does not cite CISA KEV listing or active exploitation. Exploitation is described as local, so risk depends on an attacker already being able to run code as an unprivileged process on the device.
Researcher notes
Evidence supports CWE-787 out-of-bounds write from integer overflow in String16.cpp. The CVE record gives affected Android versions and CVSS details, but the bundle does not include patch commit details, proof of concept, or exploitation telemetry.
Mitigation direction
- Check Google Android and Pixel May 2018 security bulletin guidance.
- Apply vendor-provided Android security updates for affected versions.
- Prioritize unsupported Android 6 through 8.1 devices for replacement or isolation.
- Restrict installation and execution of untrusted applications on affected devices.
Validation and detection
- Inventory Android device versions and security patch levels.
- Confirm whether devices run Android 6 through 8.1.
- Compare patch levels against Google Pixel May 2018 bulletin guidance.
- Review mobile EDR or MDM telemetry for untrusted local app execution.
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.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2017-13323 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
- High
- CVSS
- 8.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/docs/security/bulletin/pixel/2018-05-01CVE reference
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.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.