LiveActive security incident?Get immediate response
CVE Record

CVE-2017-18678: An issue was discovered on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.x) software.

An issue was discovered on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.x) software. An attacker can crash system processes via a Serializable object because of missing exception handling. The Samsung IDs are SVE-2017-8109, SVE-2017-8110, SVE-2017-8115, SVE-2017-8118, and SVE-2017-8119 (April 2017).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE affects older Samsung mobile software generations from Android 4.4 through 7.x. A malformed Serializable object can crash system processes because exceptions were not handled properly. The public record does not provide severity, CVSS scoring, or evidence of data theft or code execution.

Executive priority

Treat this as a legacy mobile hygiene issue unless affected devices still support business operations. Priority rises where old Samsung devices handle sensitive workflows or cannot receive vendor security updates.

Technical view

CVE-2017-18678 maps to Samsung SVE-2017-8109, SVE-2017-8110, SVE-2017-8115, SVE-2017-8118, and SVE-2017-8119 from April 2017. The flaw is missing exception handling around Serializable object processing, allowing process crash behavior on listed Samsung mobile software versions.

Likely exposure

Exposure is most likely limited to Samsung mobile devices still running KK 4.4, L 5.0/5.1, M 6.0, or N 7.x software. The source bundle does not identify specific device models or builds.

Exploitation context

The provided sources do not support active exploitation. The KEV flag is false, and the CVE record describes denial-of-service style process crashes rather than confirmed compromise or privilege escalation.

Researcher notes

The public record is sparse: no CVSS, CWE, model list, exploit narrative, or explicit remediation text is included. Analysis should stay tied to Samsung bulletin coverage and the named Android generation exposure.

Mitigation direction

  • Check Samsung's April 2017 mobile security guidance for the listed SVE IDs.
  • Apply available Samsung firmware or security updates to affected mobile devices.
  • Retire or isolate unsupported Samsung devices stuck on Android 4.4 through 7.x.
  • Use MDM inventory to prioritize devices with outdated Android security patch levels.

Validation and detection

  • Inventory Samsung mobile devices by Android version and security patch level.
  • Confirm whether device builds include Samsung's April 2017 security fixes.
  • Map findings to SVE-2017-8109, 8110, 8115, 8118, and 8119.
  • Review device stability telemetry for unexplained system process crash patterns.
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.

cve · low confidence lookup

CVE-2017-18678 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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