LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9403: In the MTK_FLP_MSG_HAL_DIAG_REPORT_DATA_NTF handler of flp2hal_- interface.c, there is a possible stack...

In the MTK_FLP_MSG_HAL_DIAG_REPORT_DATA_NTF handler of flp2hal_- interface.c, there is a possible stack buffer overflow due to a missing bounds check. This could lead to local escalation of privilege in a privileged process 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-9403 is a local Android privilege escalation issue. A logged-in or already-running local attacker could potentially abuse a stack buffer overflow in a privileged process to gain System-level privileges. The supplied sources do not show remote exploitation or active exploitation.

Executive priority

Treat this as high priority for fleets with older Android devices. It is not described as remotely exploitable, but successful exploitation could give System-level control on affected devices, making timely patch validation important.

Technical view

The flaw is a missing bounds check in the MTK_FLP_MSG_HAL_DIAG_REPORT_DATA_NTF handler in flp2hal_interface.c, causing a possible stack buffer overflow. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Android builds containing the affected kernel/component path referenced by the vendor record. The supplied data does not identify specific device models, OEM firmware versions, or patch levels beyond the referenced Pixel bulletin.

Exploitation context

The source bundle says exploitation requires local access and System execution privileges are the target outcome. It does not provide evidence of public exploitation, exploitation in the wild, or CISA KEV listing.

Researcher notes

Evidence is sparse. The record identifies CWE-120, a stack buffer overflow, and a local privilege-escalation impact path. The supplied affected data is broad and does not enumerate exact SKUs, kernel versions, commits, or fixed build identifiers.

Mitigation direction

  • Check Google and device OEM guidance for CVE-2018-9403 applicability.
  • Update affected Android or Pixel devices to a build containing the vendor fix.
  • Prioritize managed devices that are old, unsupported, or missing Android security updates.
  • Restrict installation and execution of untrusted local applications where possible.

Validation and detection

  • Inventory Android and Pixel devices under management.
  • Compare device patch levels against the referenced 2018-06-01 Pixel bulletin.
  • Confirm OEM firmware advisories map CVE-2018-9403 to deployed builds.
  • Flag unsupported devices that cannot receive relevant security updates.
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-120: 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-9403 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-9403Attack 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-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.