Security readout for executives and security teams
Plain-English summary
CVE-2017-13165 is a local Android kernel file-system privilege-escalation issue. A low-privileged user or app on an affected device could gain more access than intended. It is not described as remotely exploitable in the provided sources, but it matters because kernel privilege bugs can turn a limited compromise into broader device control.
Executive priority
Handle as a moderate legacy mobile risk. It is not presented as active exploitation, but unpatched Android devices can let a limited foothold become deeper device compromise.
Technical view
The CVE describes an Android kernel file-system elevation-of-privilege vulnerability, mapped to CWE-269. CVSS 3.1 is 5.3 with local access, low complexity, low privileges, no user interaction, unchanged scope, and low confidentiality, integrity, and availability impact. Public technical detail in the bundle is limited.
Likely exposure
Exposure is most likely on Android devices running affected Android kernel builds that did not receive the December 2017 Pixel/Android security fix or equivalent vendor update.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. Based on the CVSS vector, exploitation requires local access or already-running low-privileged code on the device.
Researcher notes
The public bundle is sparse: it identifies Android kernel file-system EoP, CWE-269, CVSS vector, and Pixel bulletin reference, but not root cause, affected kernel branches, or exploit details. Avoid assuming broader Android versions beyond the stated Android kernel scope.
Mitigation direction
Confirm whether fleet devices received the December 2017 Pixel/Android security update or later equivalent updates.
Check device vendor advisories for CVE-2017-13165 coverage.
Prioritize unsupported or unpatched Android devices for replacement or isolation.
Restrict installation of untrusted apps on devices that cannot be updated.
Validation and detection
Inventory Android devices and record OS build, kernel version, and security patch level.
Compare patch status against the December 2017 Pixel security bulletin and vendor guidance.
Review mobile device management data for unsupported or stale Android builds.
Treat unknown patch status as unresolved until verified from vendor or device telemetry.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-269 · source CWE mapping
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.