LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9348: In SMF_ParseMetaEvent of eas_smf.c, there is a possible integer overflow.

In SMF_ParseMetaEvent of eas_smf.c, there is a possible integer overflow. This could lead to remote denial of service due to resource exhaustion with no additional execution privileges needed. User interaction is needed for exploitation.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Android flaw can make affected devices run out of resources while parsing SMF metadata. The expected impact is denial of service, not data theft or code execution. Public records list it as high severity, with no privileges required, and the description says user interaction is needed.

Executive priority

Prioritize remediation for legacy Android fleets because the impact is availability loss and the affected versions are old. This is not presented as active exploitation in the provided sources.

Technical view

CVE-2018-9348 is an integer overflow in SMF_ParseMetaEvent in eas_smf.c. The documented consequence is remote denial of service through resource exhaustion. The CVE metadata lists CWE-190 and Android 6, 6.0.1, 7, 8, 8.1, nyc-mr1-dev, and nyc-mr2-dev as affected.

Likely exposure

Exposure is most likely on older or unpatched Android devices in the listed versions. Organizations with unmanaged mobile fleets, embedded Android deployments, or legacy devices are more likely to retain affected builds.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The CVE description says user interaction is needed, while the supplied CVSS vector says UI:N; treat this as an evidence discrepancy until confirmed from vendor data.

Researcher notes

The record identifies integer overflow and resource exhaustion, but does not include exploit details, patch diff context, or affected component reachability. The user-interaction mismatch between description and CVSS should be resolved before precise exposure scoring.

Mitigation direction

  • Check Google and OEM guidance for updates covering the June 2018 Android bulletin.
  • Patch or retire affected Android versions where vendor updates are available.
  • Restrict use of unsupported legacy Android devices in managed environments.
  • Reduce exposure to untrusted media or file-handling workflows on affected devices.

Validation and detection

  • Inventory Android devices and map OS versions against the affected version list.
  • Confirm installed Android security patch level with OEM management data.
  • Review mobile fleet records for unsupported Android 6, 7, 8, and 8.1 devices.
  • Check vendor advisories before declaring a device remediated.
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-190: 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-9348 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2018-9348Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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
GoogleAndroid6, 6.0.1, 7, 8, 8.1, nyc-mr1-dev, nyc-mr2-devunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.