Security readout for executives and security teams
Plain-English summary
This affects older Samsung mobile devices running M(6.x) or N(7.x) software. The issue involves Samsung’s DeviceTest application accepting a crafted AT command delivered through an NFC tag. Public sources do not provide severity, CVSS, impact detail, or confirmed exploitation.
Executive priority
Treat this as a legacy mobile exposure management issue, not a confirmed emergency. Prioritize finding old Samsung Android 6.x or 7.x devices, confirming patch status, and replacing unsupported devices used for business access.
Technical view
CVE-2018-21092 maps to Samsung SVE-2017-10885 from the January 2018 Samsung mobile security context. The public description says a crafted AT command may be sent by the DeviceTest application via an NFC tag on Samsung M(6.x) and N(7.x) devices. No CWE, CVSS, detailed impact, or patch mechanics are provided.
Likely exposure
Exposure is most likely limited to legacy Samsung mobile devices on M(6.x) or N(7.x) software. The bundle does not identify exact models, CPEs, carrier builds, or whether all such devices include the affected DeviceTest behavior.
Exploitation context
The source bundle does not show CISA KEV listing or any cited active exploitation. The described path requires a crafted NFC tag interacting with the DeviceTest application, but public details are too sparse to assess practical exploitability.
Researcher notes
Public evidence is thin: no CVSS, CWE, model list, exploit status, or detailed impact is included. Analysis should avoid assuming privilege level, data exposure, or universal model impact beyond Samsung M(6.x)/N(7.x) devices and the DeviceTest/NFC-tag description.
Mitigation direction
- Check Samsung guidance for SVE-2017-10885 and apply applicable mobile security updates.
- Inventory Samsung devices still running M(6.x) or N(7.x) software.
- Retire or isolate legacy devices that cannot receive relevant Samsung security updates.
- Review whether NFC is required on exposed legacy devices before leaving it enabled.
Validation and detection
- Identify Samsung mobile assets and record software version, model, and patch level.
- Confirm whether any devices remain on M(6.x) or N(7.x).
- Compare device patch levels against Samsung’s January 2018 SVE-2017-10885 guidance.
- Document unsupported or unpatchable devices for risk acceptance or replacement.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2018-21092 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://security.samsungmobile.com/securityUpdate.smsbCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.