LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9419: 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 with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9419 is a high-severity Android flaw that could let a remote attacker disclose information from affected devices without user interaction or privileges. The evidence names Android 7, 8, 8.1, and related development branches as affected.

Executive priority

Treat this as a legacy mobile fleet risk. It is not supported by evidence of known active exploitation, but the impact is high and exploitation requires no user action. Unsupported Android devices should be upgraded, patched, or removed from sensitive environments.

Technical view

The issue is described in Android Bluetooth LE L2CAP signaling handling, specifically l2cble_process_sig_cmd in l2c_ble.cc. A missing bounds check may cause an out-of-bounds read, leading to remote information disclosure. The CVSS 3.1 score is 7.5 with network attack vector, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is most likely on legacy Android 7, 8, and 8.1 devices that have not received vendor security updates covering the Android July 2018 bulletin. Modern supported Android builds are not identified as affected in the provided bundle.

Exploitation context

The bundle does not cite active exploitation, and KEV status is false. The vulnerability is still operationally relevant for unmanaged or unsupported Android fleets because exploitation requires no privileges and no user interaction, but the sources do not provide exploit details.

Researcher notes

The public description points to a missing bounds check in l2cble_process_sig_cmd. The bundle lists CWE-787, while the vulnerability text describes an out-of-bounds read; treat the exact weakness classification cautiously and rely on vendor guidance for remediation details.

Mitigation direction

  • Identify Android 7, 8, and 8.1 devices in managed and unmanaged fleets.
  • Review the Android July 2018 Security Bulletin and device vendor guidance.
  • Apply vendor-provided Android security updates where available.
  • Retire or isolate unsupported devices that cannot receive relevant security updates.
  • Limit exposure of legacy Android devices pending vendor remediation confirmation.

Validation and detection

  • Inventory Android OS versions and security patch levels across mobile assets.
  • Confirm whether affected devices received updates tied to the July 2018 bulletin.
  • Check MDM records for legacy Android 7, 8, and 8.1 devices.
  • Prioritize validation for devices handling sensitive business or customer data.
  • Document exceptions where vendor support or patch evidence is unavailable.
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-9419 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2018-9419Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/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, 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-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.