LiveActive security incident?Get immediate response
CVE Record

CVE-2018-21067: An issue was discovered on Samsung mobile devices with M(6.0) software.

An issue was discovered on Samsung mobile devices with M(6.0) software. There is an information disclosure in a Trustlet because an address is logged. The Samsung ID is SVE-2018-11600 (July 2018).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a Samsung mobile device flaw where a Trustlet logged an address, creating an information disclosure risk. The available sources do not provide CVSS, impacted model list, or exploit impact details, so urgency depends on whether the organization still has Samsung devices running M(6.0) software.

Executive priority

Treat this as an asset hygiene issue unless Samsung M(6.0) devices remain in business use. The key decision is whether legacy mobile devices still access corporate data.

Technical view

CVE-2018-21067 is tied to Samsung SVE-2018-11600 from July 2018. The reported issue is information disclosure in a Trustlet caused by logging an address. The bundle does not identify affected models, privilege requirements, attack vector, or a specific remediation beyond Samsung's security update reference.

Likely exposure

Likely limited to Samsung mobile devices running M(6.0) software. Exposure cannot be narrowed further from the provided sources because affected models and builds are not listed.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked as CISA KEV. Exploitability details are not provided.

Researcher notes

The source data is sparse: no CVSS, CWE, affected model list, attack vector, or patch identifier is included. Analysis should stay anchored to Samsung SVE-2018-11600 and vendor guidance.

Mitigation direction

  • Check Samsung's July 2018 security update guidance for SVE-2018-11600.
  • Inventory Samsung mobile devices still running M(6.0) software.
  • Update affected devices using vendor-supported firmware where available.
  • Retire or restrict unsupported devices that cannot receive security updates.

Validation and detection

  • Confirm whether managed Samsung devices run M(6.0) software.
  • Map device models and firmware builds against Samsung's security update guidance.
  • Verify mobile management records show applied Samsung security updates after July 2018.
  • Document any unsupported devices and compensating access restrictions.
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-2018-21067 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.