CVE-2018-9358: Google Inc. Android vulnerability

CVE-2018-9358: In gatts_process_attribute_req of gatt_sc.cc, there is a possible read of uninitialized data due to a missi...

In gatts_process_attribute_req of gatt_sc.cc, there is a possible read of uninitialized data due to a missing bounds check. This could lead to remote information disclosure in the Bluetooth process with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android ID: A-73172115.

UnknownCVSS not scoredNot KEV-listedUpdatedSep 17, 2024, 00:06 UTC (UTC+00:00)

Security readout for executives and security teams

This Android Bluetooth flaw could let a nearby remote attacker disclose information from the Bluetooth process without user interaction. The sources do not provide CVSS scoring or evidence of active exploitation, so urgency depends on whether legacy Android 6.0 through 8.1 devices remain in use and unpatched. Exposure is most likely on legacy Android devices running affected 6.x, 7.x, or 8.x releases without the relevant Android or OEM security update. Bluetooth must be relevant to the environment; the bundle does not identify non-Android products. Treat this as a legacy-device hygiene issue with moderate urgency. It is remotely reachable over Bluetooth and needs no user interaction, but sources do not show active exploitation or severity scoring. Focus on finding and updating or replacing affected Android devices. Mitigation focus: Apply the Android June 2018 security bulletin update or later vendor-equivalent update.; Confirm OEM firmware includes the fix for Android ID A-73172115.; Retire or isolate unsupported Android 6.x through 8.x devices..

Prepared: Jun 6, 2026, 22:26 UTC (UTC+00:00)

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.

cve · low confidence lookup

CVE-2018-9358 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: Unknown
CVSS: Not scored
Known Exploited: No
Published: Nov 6, 2018, 17:00 UTC (UTC+00:00)

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.

0CVSS vectors

0Timeline events

0ADP providers

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://source.android.com/security/bulletin/2018-06-01CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

Google Inc.AndroidAndroid-6.0 Android-6.0.1 Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1Listed

Weakness

CWE details

No CWE listed

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