LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9414: In gattServerSendResponseNative of com_android_bluetooth_gatt.cpp, there is a possible out of bounds stack...

In gattServerSendResponseNative of com_android_bluetooth_gatt.cpp, there is a possible out of bounds stack write due to a missing bounds check. This could lead to local escalation of privilege with User 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

This is a high-severity Android Bluetooth component flaw that could let code already running as a user gain higher local privileges. It affects listed Android 6 through 8.1 versions. The source bundle does not show active exploitation, and it does not name affected products beyond Google Android.

Executive priority

Treat as a high-priority legacy Android remediation issue, especially for managed fleets with Android 6 through 8.1 devices. Business urgency is lower than a remote exploited bug, but local privilege escalation can materially increase impact after initial compromise.

Technical view

CVE-2018-9414 is a CWE-787 out-of-bounds stack write in Android's gattServerSendResponseNative within com_android_bluetooth_gatt.cpp. The issue stems from a missing bounds check and is scored CVSS 7.8. Exploitation is local, low complexity, requires low privileges, and does not require user interaction.

Likely exposure

Exposure is most likely on legacy Android 6, 6.0.1, 7, 7.1.1, 7.1.2, 8, and 8.1 devices that have not received the relevant vendor security update. The provided data marks other versions as unaffected by default.

Exploitation context

The CVE describes local privilege escalation from user execution privileges. No user interaction is needed. The bundle says KEV is false and provides no cited evidence of active exploitation, public exploit use, or remote attackability.

Researcher notes

Analysis is limited to the supplied CVE and Android bulletin reference. The bundle does not include patch commit details, exploit telemetry, or proof-of-concept status. Avoid assuming Bluetooth proximity exploitation; the CVSS vector and description support local privilege escalation only.

Mitigation direction

  • Identify devices running the affected Android versions.
  • Check Google and OEM security bulletins for the applicable fix.
  • Apply relevant Android or Pixel security updates where available.
  • Retire or isolate unsupported devices that cannot be updated.
  • Restrict untrusted local app installation on exposed devices.

Validation and detection

  • Inventory Android OS versions and security patch levels.
  • Confirm whether devices match the listed affected versions.
  • Compare device patch status against Google and OEM bulletins.
  • Review mobile EDR or MDM data for legacy Android exposure.
  • Document unsupported devices requiring replacement or compensating controls.
Prepared
Confidence
high
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-9414 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-9414Attack 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
GoogleAndroid6, 6.0.1, 7, 7.1.1, 7.1.2, 8, 8.1unaffected
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.