LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9435: In gatt_process_error_rsp of gatt_cl.cc, there is a possible out of bound read due to a missing bounds check.

In gatt_process_error_rsp of gatt_cl.cc, there is a possible out of bound read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 6.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9435 is an Android Bluetooth stack flaw that can expose information from memory. The sources describe local information disclosure without user interaction or extra privileges. The main business concern is legacy Android devices that missed the August 2018 Android/Pixel security update.

Executive priority

Treat as a moderate legacy-device hygiene issue. It is not cited as actively exploited, but affected devices are old and may lack other critical fixes, making retirement or update enforcement the practical priority.

Technical view

The issue is a missing bounds check in gatt_process_error_rsp in gatt_cl.cc, classified as CWE-125 out-of-bounds read. It affects Android 6, 6.0.1, 7, 7.1.1, 7.1.2, 8, and 8.1. CVSS 3.1 is 6.2 with local attack vector and high confidentiality impact only.

Likely exposure

Exposure is most likely on unmanaged, unsupported, or custom Android builds running the listed Android 6 through 8.1 versions without the relevant 2018 security bulletin fixes.

Exploitation context

The provided sources and KEV flag do not show active exploitation. The CVSS vector requires local access, no privileges, and no user interaction. The source bundle does not provide exploit details, prerequisites beyond locality, or proof-of-concept status.

Researcher notes

Evidence is limited to the CVE description, affected Android versions, CVSS vector, CWE-125 classification, and the Android/Pixel bulletin reference. Do not infer remote Bluetooth exploitation or specific patch mechanics beyond vendor guidance.

Mitigation direction

  • Apply the Android or Pixel security update referenced by the vendor bulletin.
  • Retire or isolate devices that cannot receive supported Android security updates.
  • For custom Android builds, verify the vendor has backported the gatt_cl.cc fix.
  • Prioritize managed devices with Bluetooth enabled and sensitive enterprise access.

Validation and detection

  • Inventory Android devices and identify versions 6 through 8.1.
  • Check each device security patch level against the August 2018 Android/Pixel bulletin.
  • Review custom ROM or OEM firmware changelogs for this CVE or Bluetooth GATT fixes.
  • Confirm unsupported devices are removed from sensitive access groups.
Prepared
Confidence
high
Sources
3

Public sources used

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-125: 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-9435 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.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

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-125

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs