LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9462: In store_cmd of ftm4_pdc.c, there is a possible out of bounds write due to an incorrect bounds check.

In store_cmd of ftm4_pdc.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System 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-9462 is an Android kernel flaw in ftm4_pdc.c where an incorrect bounds check can allow an out-of-bounds write. The business concern is local privilege escalation: an attacker with local low-level access could potentially gain higher privileges without user interaction.

Executive priority

Treat this as a high-priority legacy Android patching issue, not an internet-facing emergency. The key risk is compromised local access becoming higher privilege on vulnerable devices.

Technical view

The issue is in store_cmd of ftm4_pdc.c and is classified as CWE-787. CVSS 3.1 is 7.8, with local attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to Android kernel builds containing the vulnerable ftm4_pdc.c code path. The provided sources reference Google Android Kernel and the Pixel August 2018 security bulletin, but do not enumerate every affected device model or build.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation is described as local, requiring privileges but no user interaction. No exploit details are provided in the sources.

Researcher notes

Evidence supports a local Android kernel out-of-bounds write in store_cmd. The sources do not provide device-specific affected ranges, exploit availability, or standalone mitigations beyond vendor security bulletin tracking.

Mitigation direction

  • Check Google and device-vendor guidance for CVE-2018-9462 patch status.
  • Verify Android security patch levels against the August 2018 Pixel bulletin.
  • Prioritize updates for devices handling sensitive data or privileged enterprise access.
  • Retire or isolate Android devices that cannot receive relevant security updates.

Validation and detection

  • Inventory Android devices and record model, kernel build, and security patch level.
  • Compare device patch status with Google Pixel August 2018 bulletin guidance.
  • Confirm vulnerability scanners map findings specifically to CVE-2018-9462.
  • Review mobile fleet compliance for outdated or unsupported Android builds.
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-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 lookup
cve · low confidence lookup

CVE-2018-9462 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-9462Attack 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
GoogleAndroidKernelunaffected
Weakness

CWE details

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

CWE-787 · source CWE mapping

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.