LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9350: In ih264d_assign_pic_num of ih264d_utils.c there is a possible out of bound read due to missing bounds check.

In ih264d_assign_pic_num of ih264d_utils.c there is a possible out of bound read due to missing bounds check. This could lead to a denial of service 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-9350 is an Android media-decoder flaw that can crash affected devices or services when a user interacts with malicious content. The available sources describe denial of service only, not data theft or code execution. The listed affected Android versions are 7, 7.1.1, 7.1.2, 8, and 8.1.

Executive priority

Treat this as a moderate availability risk for legacy Android fleets. It is not described as data theft or remote code execution, but unsupported or unpatched devices can still create operational disruption if users process malicious media.

Technical view

The issue is a CWE-125 out-of-bounds read in ih264d_assign_pic_num within ih264d_utils.c, caused by a missing bounds check. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, required user interaction, and high availability impact.

Likely exposure

Exposure is most relevant to devices running the listed Android 7.x or 8.x versions that process attacker-supplied media through the affected decoder path. The source bundle does not identify other vendors, downstream products, or specific delivery formats.

Exploitation context

The CVE data says exploitation requires user interaction and no additional execution privileges. The source bundle does not show CISA KEV listing, active exploitation, public exploit details, or confirmed weaponization.

Researcher notes

Evidence is limited to the CVE record and Android bulletin reference. The affected code path points to H.264 decoding, but the bundle does not provide patch diff details, exploit samples, or downstream device coverage. Avoid claiming active exploitation without additional evidence.

Mitigation direction

  • Review the Android or Pixel June 2018 bulletin for vendor remediation guidance.
  • Update affected Android devices to vendor-supported security patch levels.
  • Prioritize unsupported Android 7.x and 8.x devices for replacement or isolation.
  • Limit exposure to untrusted media where immediate patching is not possible.

Validation and detection

  • Inventory Android devices and record OS versions and patch levels.
  • Identify devices running Android 7, 7.1.1, 7.1.2, 8, or 8.1.
  • Compare patch status against the referenced Android or Pixel security bulletin.
  • Confirm media-handling apps are updated through vendor-approved channels.
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-9350 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:N/I:N/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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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-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.