LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9392: In get_binary of vendor/mediatek/proprietary/hardware/connectivity/gps/gps_hal/src/data_coder.c, there is a...

In get_binary of vendor/mediatek/proprietary/hardware/connectivity/gps/gps_hal/src/data_coder.c, there is a possible out of bounds write due to a missing 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-9392 is a high-severity Android issue tied to MediaTek GPS HAL code. A local attacker with existing low privileges could potentially gain System-level control. It does not require user interaction, but the source bundle does not show remote exploitation or active exploitation.

Executive priority

Treat as a high-priority mobile fleet patch validation item, especially for older Android or MediaTek-based devices. Business urgency is lower than remotely exploitable vulnerabilities because local access is required and active exploitation is not evidenced.

Technical view

The flaw is an out-of-bounds write in get_binary within vendor/mediatek/proprietary/hardware/connectivity/gps/gps_hal/src/data_coder.c, caused by a missing bounds check. It maps to CWE-787 and has CVSS 3.1 score 7.8 with local attack vector, low complexity, low privileges, and high CIA impact.

Likely exposure

Exposure appears limited to Android builds or device firmware containing the referenced MediaTek proprietary GPS HAL path. The bundle lists Google Android Kernel but also marks default status unaffected, so affected device scope should be confirmed against vendor and OEM bulletins.

Exploitation context

No KEV listing is provided and the bundle contains no evidence of active exploitation. Exploitation is local, requires existing privileges, needs no user interaction, and could result in System execution privileges if successfully abused.

Researcher notes

The source evidence is sparse and does not provide a fixed commit, exploit details, or definitive affected-device matrix. Avoid broad product claims beyond Android builds containing the referenced MediaTek GPS HAL component and validate against vendor firmware provenance.

Mitigation direction

  • Apply relevant Android or Pixel security updates from the June 2018 bulletin where applicable.
  • Check OEM firmware guidance for devices using MediaTek GPS HAL components.
  • Prioritize remediation on managed Android devices with outdated security patch levels.
  • Restrict untrusted app installation while patch status is being confirmed.

Validation and detection

  • Inventory Android devices and record vendor, chipset, firmware, and Android security patch level.
  • Compare device patch levels against the Pixel June 2018 security bulletin and OEM advisories.
  • Confirm whether device firmware includes the referenced MediaTek GPS HAL code path.
  • Track remediation evidence through MDM, EDR, or mobile fleet management reporting.
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-9392 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-9392Attack 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.