LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9485: In l2cble_process_sig_cmd of l2c_ble.cc, there is a possible out of bounds read due to a missing bounds check.

In l2cble_process_sig_cmd of l2c_ble.cc, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disclosure over bluetooth with no additional execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Android Bluetooth flaw could let a nearby attacker read sensitive memory from affected devices without user interaction. It is not internet-routable, but it matters for fleets with older Android devices or unmanaged Bluetooth exposure.

Executive priority

Treat as a moderate fleet hygiene issue. Prioritize legacy Android devices used near sensitive people, facilities, or data, but do not treat it as proven widespread exploitation from these sources.

Technical view

CVE-2018-9485 is a CWE-125 out-of-bounds read in Android's l2cble_process_sig_cmd in l2c_ble.cc. The CVSS vector is AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, reflecting adjacent Bluetooth access and high confidentiality impact only.

Likely exposure

Exposure is most likely on Android 7, 8, 8.1, and 9 devices, including listed development branches, that have not received the relevant Android security update.

Exploitation context

The source states remote information disclosure over Bluetooth with no privileges or user interaction. KEV is false, and the provided sources do not establish active exploitation.

Researcher notes

The available evidence identifies the vulnerable function and impact class, but does not provide exploit details or device-specific patch matrices. Validation should focus on patch level, Android version, and vendor support status.

Mitigation direction

  • Apply Android security updates from the September 2018 bulletin or later vendor-supported builds.
  • Retire or isolate affected Android versions where patch status cannot be verified.
  • Restrict Bluetooth use on unsupported devices that must remain in service.
  • Check device vendor guidance for model-specific patch availability and backports.

Validation and detection

  • Inventory Android version, build, and security patch level across managed devices.
  • Compare devices against Google's September 2018 Android Security Bulletin guidance.
  • Prioritize validation for devices with Bluetooth enabled in sensitive environments.
  • Confirm compensating controls for devices that cannot be patched or retired.
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-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-9485 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.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:A/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid7, 8, 8.1, 9, nyc-mr1-dev, nyc-mr2-devunaffected
Weakness

CWE details

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.