LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9464: In multiple locations, there is a possible way to read protected files due to a missing permission check.

In multiple locations, there is a possible way to read protected files due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9464 is an Android kernel issue where missing permission checks may let a local attacker read protected files. Google describes possible local privilege escalation with no user interaction. The source bundle does not identify exact vulnerable kernel versions, affected device models, or active exploitation.

Executive priority

Prioritize remediation for legacy or unmanaged Android fleets, especially devices with enterprise access. The risk is high because compromise could affect confidentiality, integrity, and availability, but urgency is moderated by the absence of cited active exploitation evidence.

Technical view

The vulnerability is reported in multiple Android kernel locations and is associated with protected-file access caused by missing permission checks. CVSS 3.1 is 7.8, local attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most relevant to Android devices running affected kernel builds before the relevant Google Pixel security bulletin remediation. The provided affected data names Google Android Kernel but does not list exact versions, device models, or CPEs.

Exploitation context

The bundle marks KEV as false and cites no active exploitation. Exploitation is local, requires low privileges, and does not require user interaction. No exploit method or public weaponization evidence is provided in the sources.

Researcher notes

Evidence is thin: the CVE text gives impact and prerequisites but not exact vulnerable code paths, affected version ranges, or fix commits. The listed CWE-125 does not fully align with the missing-permission-check description, so validate against vendor bulletin data before scoping.

Mitigation direction

  • Apply the relevant Android or Pixel security update covering CVE-2018-9464.
  • Check device vendor guidance for exact fixed patch levels and supported models.
  • Retire or isolate unsupported Android devices that cannot receive the fix.
  • Limit installation of untrusted local applications on unpatched devices.
  • Prioritize devices handling sensitive data or privileged enterprise access.

Validation and detection

  • Inventory Android devices, kernel versions, models, and security patch levels.
  • Compare patch levels with Google Pixel August 2018 bulletin guidance.
  • Confirm CVE-2018-9464 remediation status in MDM or vulnerability management records.
  • Identify unsupported devices that cannot receive vendor security updates.
  • Review unpatched devices for exposure to untrusted local applications.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-125: 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 lookup
cve · low confidence lookup

CVE-2018-9464 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2018-9464Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidAndroid Kernelunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.