LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9484: In l2cu_send_peer_config_rej of l2c_utils.cc, there is a possible out of bounds read due to a missing bound...

In l2cu_send_peer_config_rej of l2c_utils.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-9484 is an Android information-disclosure flaw. A remote attacker could trigger an out-of-bounds read without user interaction or privileges, potentially exposing sensitive memory data. The provided sources identify affected Android 7, 8, 8.1, 9, and listed development branches.

Executive priority

Treat this as high priority for legacy Android fleets. It affects confidentiality and requires no user action, but current exploitation evidence was not provided. Focus on patch verification and unsupported-device reduction.

Technical view

The flaw is a CWE-125 out-of-bounds read in l2cu_send_peer_config_rej in l2c_utils.cc, caused by a missing bounds check. CVSS 3.1 is 7.5: network, low complexity, no privileges, no user interaction, unchanged scope, high confidentiality impact only.

Likely exposure

Exposure is most likely on older or unpatched Android devices running affected Android 7, 8, 8.1, or 9 builds. Device-specific exposure depends on OEM backports and installed Android security patch levels.

Exploitation context

The supplied bundle does not show KEV status or any cited evidence of active exploitation. Risk is still meaningful because the CVSS vector indicates remote reachability, low attack complexity, and no required user interaction.

Researcher notes

The evidence points to a bounds-check failure in Android l2c_utils.cc leading to remote information disclosure. The bundle does not provide exploit details, proof-of-concept status, or device-specific patch mappings, so validation should stay tied to vendor bulletins and build metadata.

Mitigation direction

  • Check Google and device-vendor guidance for CVE-2018-9484 updates.
  • Update affected Android devices to vendor-supported patched builds.
  • Retire or isolate devices that cannot receive security updates.
  • Prioritize managed fleets still running Android 7 through 9.

Validation and detection

  • Inventory Android versions and security patch levels across managed devices.
  • Compare device builds against the September 2018 Android security bulletin.
  • Confirm OEM firmware includes the relevant Android security fixes.
  • Track unsupported devices as residual exposure until replaced or isolated.
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-9484 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-9484Attack 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, 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.