CVE-2018-9359: Google Inc. Android vulnerability

CVE-2018-9359: In process_l2cap_cmd of l2c_main.cc, there is a possible out of bounds read due to a missing bounds check.

In process_l2cap_cmd of l2c_main.cc, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure 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-74196706.

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

Security readout for executives and security teams

CVE-2018-9359 is an Android Bluetooth/L2CAP parsing flaw that may let a nearby remote attacker read memory from a vulnerable device. The source states no user interaction or extra privileges are required. The business concern is older, unpatched Android devices still in service, not modern fully updated devices. Exposure is most likely in fleets with Android 6.0 through 8.1 devices that did not receive the relevant June 2018 Android security bulletin fixes from Google or the OEM. Unsupported rugged devices, kiosks, scanners, and BYOD handsets are higher concern. Treat this as a legacy Android fleet hygiene issue with moderate urgency. Prioritize devices that are unsupported, business-critical, or hard to monitor. There is no sourced evidence of active exploitation in the supplied bundle. Mitigation focus: Apply vendor-supported Android security updates covering the June 2018 bulletin.; Confirm OEM firmware includes a fix for Android ID A-74196706.; Retire or isolate unsupported Android 6.0 through 8.1 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-9359 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.