LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9351: In ih264e_fmt_conv_420p_to_420sp of ih264e_fmt_conv.c there is a possible out of bound read due to missing...

In ih264e_fmt_conv_420p_to_420sp of ih264e_fmt_conv.c there is a possible out of bound read due to missing bounds check. This could lead to remote 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-9351 is an Android media-processing flaw that can crash affected devices or services after user interaction. The public record describes availability impact, not data theft or code execution. Business urgency is mainly for fleets still running Android 7.x or 8.x builds without the relevant 2018 security update path.

Executive priority

Treat this as a moderate legacy Android fleet risk. It is not evidenced as exploited or code-executing, but it can disrupt affected devices. Priority should focus on inventory accuracy, patch-level confirmation, and removal of unsupported Android 7.x or 8.x devices from sensitive workflows.

Technical view

The flaw is an out-of-bounds read in ih264e_fmt_conv_420p_to_420sp in ih264e_fmt_conv.c, caused by missing bounds checking. It is classified as CWE-125. CVSS 3.1 is 6.5: network-reachable, low complexity, no privileges, user interaction required, unchanged scope, and high availability impact only.

Likely exposure

Exposure is most plausible on Android 7, 7.1.1, 7.1.2, 8, and 8.1 systems that can process attacker-supplied media or content reaching the affected H.264 conversion path. Modern, patched, or unsupported-device status is not established by the source bundle and must be verified per device build.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation evidence. Exploitation is described as remote denial of service with no additional privileges, but it requires user interaction. No source in the bundle supports confidentiality impact, integrity impact, or code execution.

Researcher notes

Evidence is limited to the CVE record and Android bulletin reference. The affected function points to Android H.264 encoding/conversion code, with missing bounds checking causing an out-of-bounds read. Do not assume exploitability beyond denial of service without additional vendor or researcher evidence.

Mitigation direction

  • Identify Android 7.x and 8.x devices in managed inventory.
  • Check Google Pixel June 2018 bulletin guidance and OEM security bulletins.
  • Apply available vendor security updates for affected device builds.
  • Retire or restrict devices without a supported update path.
  • Reduce exposure to untrusted media handling where updates are unavailable.

Validation and detection

  • Confirm each device Android version and security patch level.
  • Compare device builds against Google or OEM June 2018 security guidance.
  • Review MDM inventory for remaining Android 7.x and 8.x assets.
  • Validate media-facing apps and workflows on unpatched devices.
  • Track unsupported devices as residual denial-of-service risk.
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-9351 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-9351Attack 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.