Security readout for executives and security teams
Plain-English summary
This CVE concerns Samsung mobile devices running Android N(7.x) or O(8.x). The built-in Call+ application could load code from an unintended path, creating a code execution risk. The sources do not provide CVSS, affected model details, attack prerequisites, or active exploitation evidence.
Executive priority
Treat this as a legacy mobile exposure review item. Prioritize if the organization still permits Samsung Android 7.x or 8.x devices to access corporate data.
Technical view
CVE-2018-21075 maps to Samsung SVE-2017-10886 from April 2018. The issue is improper class loading path handling in the Call+ application, potentially allowing code execution. Public source data is sparse and does not define vulnerable models, required privileges, exploit chain details, or specific fixed builds.
Likely exposure
Exposure appears limited to Samsung mobile devices on Android 7.x or 8.x software with the Call+ application. The provided sources do not enumerate models, regions, carrier builds, or exact firmware versions.
Exploitation context
CISA KEV status is false, and the supplied sources cite no active exploitation. Code execution is potentially serious, but exploitability cannot be assessed from the provided evidence.
Researcher notes
The record identifies the vulnerable component and impact class but omits CVSS, CWE, model list, prerequisites, and fixed build identifiers. Further analysis should start with Samsung SVE-2017-10886 advisories and device firmware mapping.
Mitigation direction
- Check Samsung guidance for SVE-2017-10886 and apply applicable security updates.
- Inventory Samsung Android 7.x and 8.x devices in managed environments.
- Upgrade or retire unsupported affected devices where vendor fixes are unavailable.
- Restrict sensitive access from devices that cannot be verified as updated.
Validation and detection
- Confirm whether any Samsung devices still run Android 7.x or 8.x software.
- Check device patch history against Samsung's April 2018 security update guidance.
- Verify whether Call+ is present on in-scope devices.
- Document exceptions where model or firmware mapping cannot be confirmed.
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-21075 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.
