LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9429: In buildImageItemsIfPossible of ItemTable.cpp there is a possible out of bound read due to uninitialized data.

In buildImageItemsIfPossible of ItemTable.cpp there is a possible out of bound read due to uninitialized data. This could lead to information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9429 is an Android information disclosure flaw. Affected Android 8.1 systems may disclose sensitive data after user interaction. It does not require attacker privileges, but the public sources do not show active exploitation or provide operational exploit detail.

Executive priority

Treat this as a moderate confidentiality risk. It should be remediated through normal mobile patch governance, with higher priority for legacy Android 8.1 devices handling sensitive business data.

Technical view

The flaw is a CWE-125 out-of-bounds read in buildImageItemsIfPossible in ItemTable.cpp, caused by uninitialized data. CVSS 3.1 is 6.5: network reachable, low complexity, no privileges, user interaction required, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure appears limited to Google Android 8.1 as listed in the source bundle. Other Android versions or OEM builds should not be assumed affected without vendor confirmation.

Exploitation context

The source bundle marks KEV as false, and no cited source reports active exploitation. Exploitation requires user interaction and could disclose information; the public evidence does not identify a specific exploit path.

Researcher notes

The public record is sparse. Do not extrapolate affected products beyond Android 8.1 from the provided sources. Validation should focus on vendor bulletin mapping, device patch levels, and whether any OEM-specific builds carried the vulnerable code.

Mitigation direction

  • Check the Android or Pixel bulletin for vendor-provided update guidance.
  • Apply relevant vendor security updates to affected Android 8.1 devices.
  • Prioritize managed devices that process sensitive content or untrusted media.
  • Retire or isolate Android 8.1 devices that cannot receive security updates.

Validation and detection

  • Inventory Android devices and identify any running version 8.1.
  • Compare device patch levels against the referenced July 2018 Pixel bulletin.
  • Confirm whether OEM advisories list this CVE for each device model.
  • Document unsupported devices and compensating controls separately.
Prepared
Confidence
medium
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-9429 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:N/AC:L/PR:N/UI:R/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:N/AC:L/PR:N/UI:R/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-9429Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
GoogleAndroid8.1unaffected
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.