LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9349: In mv_err_cost of mcomp.c there is a possible out of bounds read due to missing bounds check.

In mv_err_cost of mcomp.c there is a possible out of bounds 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 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9349 is an Android out-of-bounds read issue that can crash affected devices or services. It is a denial-of-service risk, not a data theft or code execution issue based on the provided sources. Exploitation requires user interaction, lowering urgency but still warranting patch verification for older Android fleets.

Executive priority

Treat this as a moderate legacy mobile availability risk. It should not displace actively exploited or code-execution vulnerabilities, but organizations with older Android devices should verify patch coverage and remove unsupported endpoints from sensitive workflows.

Technical view

The flaw is a missing bounds check in mv_err_cost within mcomp.c, leading to a possible out-of-bounds read. CVSS 3.1 is 6.5 with network attack vector, low complexity, no privileges, required user interaction, and high availability impact. Affected Android versions listed are 7, 7.1.1, 7.1.2, 8, and 8.1.

Likely exposure

Exposure is most likely in legacy Android or Pixel environments still running Android 7.x or 8.x without the relevant vendor security update. Modern supported Android devices are less likely exposed, but the provided bundle does not confirm unaffected patch levels beyond listed affected versions.

Exploitation context

The bundle does not report active exploitation, and KEV status is false. Exploitation requires user interaction and no additional privileges. The stated impact is denial of service through an out-of-bounds read, not confidentiality or integrity compromise.

Researcher notes

Evidence is limited to the CVE record, CVE List entry, and Android Pixel bulletin reference. The bundle names the vulnerable function and affected Android versions but does not provide detailed exploit conditions, affected components, or proof of active exploitation.

Mitigation direction

  • Apply the applicable Android or Pixel security update from vendor guidance.
  • Prioritize legacy Android 7.x and 8.x devices for patch verification.
  • Retire or isolate devices that cannot receive supported security updates.
  • Monitor vendor advisories for any additional affected build or patch details.

Validation and detection

  • Inventory Android devices and record OS version and security patch level.
  • Identify devices running Android 7, 7.1.1, 7.1.2, 8, or 8.1.
  • Compare device patch status against the June 2018 Pixel security bulletin.
  • Confirm unsupported devices are removed, isolated, or risk-accepted.
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-9349 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-9349Attack 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.