LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9423: In ihevcd_parse_slice_header of ihevcd_parse_slice_header.c there is a possible out of bound read due to mi...

In ihevcd_parse_slice_header of ihevcd_parse_slice_header.c there is a possible out of bound read due to missing bounds check. This could lead to denial of service with no additional execution privileges needed. User interaction is needed for exploitation.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9423 is an Android media parsing flaw that can crash affected devices or processes when a user interacts with crafted content. The reported business impact is denial of service, not data theft or code execution. User interaction is required, and the source bundle does not show active exploitation.

Executive priority

Treat this as a moderate-priority mobile hygiene issue. It can disrupt availability on affected Android devices, but the provided evidence does not indicate confidentiality impact, integrity impact, privilege escalation, or active exploitation.

Technical view

The flaw is a CWE-125 out-of-bounds read in Android's ihevcd_parse_slice_header function, caused by a missing bounds check. CVSS 3.1 is 5.5 with local attack vector, low complexity, no privileges, required user interaction, unchanged scope, and high availability impact only.

Likely exposure

Exposure is most relevant to Android devices running listed affected versions: 7, 7.1.1, 7.1.2, 8, and 8.1. Organizations with unmanaged or unsupported Android fleets are more likely to have residual exposure.

Exploitation context

The record says exploitation needs user interaction and no additional execution privileges. KEV status is false, and the provided sources do not claim active exploitation or public weaponization.

Researcher notes

Focus review on Android HEVC media parsing and the missing bounds check in ihevcd_parse_slice_header.c. The source bundle identifies DoS from out-of-bounds read, but does not provide patch diff detail, exploit evidence, or broader product scope.

Mitigation direction

  • Check Android or Pixel vendor guidance for CVE-2018-9423 remediation details.
  • Apply applicable Android security updates to affected and supported devices.
  • Retire or isolate unsupported Android 7 through 8.1 devices where updates are unavailable.
  • Use MDM policy to enforce minimum Android security patch levels.
  • Limit use of untrusted media files on legacy Android devices.

Validation and detection

  • Inventory Android devices and identify versions 7, 7.1.1, 7.1.2, 8, and 8.1.
  • Confirm each device's Android security patch level through MDM or device settings.
  • Check vulnerability management results for CVE-2018-9423 against Android assets.
  • Review mobile crash telemetry for recurring media decoder failures on legacy devices.
  • Document exceptions for devices that cannot receive vendor updates.
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-9423 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
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/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.