LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9391: In update_gps_sv and output_vzw_debug of vendor/mediatek/proprietary/hardware/connectivity/gps/gps_hal/...

In update_gps_sv and output_vzw_debug of vendor/mediatek/proprietary/hardware/connectivity/gps/gps_hal/src/gpshal_wor ker.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.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9391 is an Android local privilege escalation issue in MediaTek GPS HAL code. A missing bounds check could allow an out-of-bounds write. The available data shows local access and high privileges are required, with no user interaction. This is not described as remotely exploitable, and there is no KEV evidence of active exploitation.

Executive priority

Treat as a moderate mobile fleet remediation item. It is serious if present because impact is high, but available evidence points to a local, high-privilege path and no confirmed active exploitation. Prioritize unsupported or lagging Android devices.

Technical view

The flaw is CWE-787 in update_gps_sv and output_vzw_debug within vendor/mediatek proprietary GPS HAL worker code. CVSS 3.1 is 6.7 with AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Impact is high for confidentiality, integrity, and availability if reachable from a privileged local context.

Likely exposure

Exposure appears limited to Android environments matching the cited Android/Pixel bulletin and affected kernel/component data. Organizations should not assume all Android devices are affected; confirm device models, OEM firmware lineage, MediaTek GPS HAL presence, and security patch level.

Exploitation context

The source bundle does not cite public exploitation, exploit availability, or KEV listing. The CVSS vector indicates local attack, low complexity, high privileges required, and no user interaction. That makes fleet hygiene important, but reduces urgency versus remote or unauthenticated flaws.

Researcher notes

Evidence is limited to the CVE record, CVE List data, and Android Pixel bulletin reference. The affected entry is broad and somewhat sparse, so product-level conclusions should be validated against OEM firmware advisories and device build information before declaring exposure.

Mitigation direction

  • Check Android and OEM guidance for CVE-2018-9391 applicability.
  • Update affected devices to vendor-supported firmware containing the relevant security fixes.
  • Prioritize managed Android devices with MediaTek GPS HAL exposure.
  • Retire devices that cannot receive applicable Android security updates.

Validation and detection

  • Inventory Android device models, chipsets, firmware builds, and patch levels.
  • Compare devices against the June 2018 Android/Pixel bulletin guidance.
  • Confirm whether the MediaTek GPS HAL component is present in affected builds.
  • Track remediation evidence in mobile device management or asset records.
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-9391 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
Medium
CVSS
6.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/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
6.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.7Medium
CVSS 3.1 vector shape for CVE-2018-9391Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/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.