LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9380: In l2c_lcc_proc_pdu of l2c_fcr.cc, there is a possible out of bounds write due to improper input validation.

In l2c_lcc_proc_pdu of l2c_fcr.cc, there is a possible out of bounds write due to improper input validation. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9380 is a high-severity Android Bluetooth-related memory corruption issue. A malformed input could cause an out-of-bounds write and potentially let a remote attacker gain elevated privileges, but exploitation requires user interaction. The provided sources do not show active exploitation.

Executive priority

Treat this as a high-priority legacy Android exposure issue. The business risk is greatest where older mobile devices still access email, identity, or internal services. Prioritize patch verification and removal of unsupported devices.

Technical view

The issue is in Android's l2c_lcc_proc_pdu function in l2c_fcr.cc. Improper input validation may allow an out-of-bounds write, mapped to CWE-787. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, scoring 8.8.

Likely exposure

Exposure is limited to Android 7, 7.1.1, 7.1.2, 8, and 8.1 as listed in the source bundle. Devices outside those listed versions are not identified as affected by the provided evidence.

Exploitation context

The vulnerability is remotely reachable with low attack complexity and no attacker privileges, but user interaction is required. It is not listed as CISA KEV in the supplied data, and no cited source claims active exploitation.

Researcher notes

The provided evidence identifies the vulnerable function and impact class but does not include exploit details, affected component reachability specifics, or device-by-device patch matrices. Avoid assuming exploitation in the wild without KEV or another cited source.

Mitigation direction

  • Apply the relevant Android or Pixel security updates from vendor guidance.
  • Prioritize unmanaged or legacy Android 7.x and 8.x devices for remediation.
  • Remove unsupported affected devices from sensitive environments if updates are unavailable.
  • Track vendor advisories for device-specific patch availability and rollout status.

Validation and detection

  • Inventory Android devices and confirm OS versions against the affected list.
  • Check each device security patch level against the vendor bulletin timeline.
  • Verify MDM compliance reporting for Android 7.x and 8.x fleets.
  • Confirm unsupported devices are isolated, replaced, or formally risk accepted.
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-9380 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
8.8 (3.1)
Known Exploited
No
Published

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

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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, 7.1.1, 7.1.2, 8, 8.1unaffected
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.