Security readout for executives and security teams
Plain-English summary
This is a high-severity Android local privilege escalation issue. A malicious or compromised app on affected Android versions could bypass permissions and start an activity with system privileges. It is not described as remotely exploitable, and the supplied sources do not show active exploitation.
Executive priority
Treat as high priority for legacy Android fleets because successful exploitation could grant system-level privileges. Risk is lower for fully patched or unsupported-unused devices, but unmanaged older devices should be identified quickly.
Technical view
The issue is in ProcessStats.java read() and is described as a read/write serialization flaw causing a permissions bypass. CVSS 3.1 is 7.8: local attack, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely on older Android 7, 8, and 8.1 devices, including listed nyc-mr1-dev and nyc-mr2-dev builds, that lack the relevant Android security update or OEM equivalent.
Exploitation context
An attacker would need local app-level access, such as a malicious installed app. User interaction is not needed after that condition. KEV is false, and the provided sources do not cite active exploitation.
Researcher notes
The source bundle identifies CWE-276 and an Android framework ProcessStats.java serialization issue. Evidence supports local privilege escalation, not remote exploitation. No exploit code, public exploitation, or device-specific remediation detail is provided beyond the Android bulletin reference.
Mitigation direction
- Apply Android security updates that include the May 2018 Android Security Bulletin fixes.
- Confirm OEM firmware for Android 7, 8, and 8.1 devices includes the relevant patch level.
- Remove or isolate unsupported devices that cannot receive vendor security updates.
- Restrict untrusted app installation and enforce managed app allowlisting where available.
- Monitor Google and OEM guidance for device-specific remediation details.
Validation and detection
- Inventory Android devices and OS versions, focusing on Android 7, 8, and 8.1.
- Check Android security patch level against the May 2018 bulletin or OEM equivalent.
- Review MDM records for unmanaged sideloading or risky app installation paths.
- Verify affected device models still receive OEM security updates.
- Prioritize this in fleets that allow third-party or unmanaged app installation.
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-276: 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-13311 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
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/security/bulletin/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.
Incorrect Default Permissions
Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.