Security readout for executives and security teams
Plain-English summary
This CVE concerns some older Samsung mobile devices where the secure screen-lock component may allow password brute forcing. The practical business risk is unauthorized access to data on affected devices, especially if devices are lost, stolen, or retained in service without old security updates.
Executive priority
Treat this as a targeted mobile device exposure issue. Prioritize devices with access to sensitive business data, executive accounts, privileged apps, or regulated information, especially if they are old or unsupported.
Technical view
CVE-2020-10849 affects Samsung devices running Android O, P, or Q software on Exynos7885, Exynos8895, and Exynos9810 chipsets. The issue is in the Gatekeeper trustlet and is tracked by Samsung as SVE-2019-14575 in the January 2020 security update context.
Likely exposure
Exposure is most likely in organizations still using affected Samsung Android 8.x, 9.0, or 10.0 devices with the listed Exynos chipsets and incomplete Samsung security patching.
Exploitation context
The provided sources do not cite active exploitation, and the CVE is not marked KEV. The sources also do not describe remote exploitation, public exploit availability, prerequisites, or attack complexity.
Researcher notes
The source bundle provides a concise vulnerability description but lacks CVSS, CWE, detailed prerequisites, patch matrix, and model-level affected lists. Avoid assuming exploitability beyond the stated Gatekeeper trustlet brute-force screen-lock issue.
Mitigation direction
- Identify Samsung devices with Android 8.x, 9.0, or 10.0 and listed Exynos chipsets.
- Check Samsung guidance for SVE-2019-14575 and relevant January 2020 security updates.
- Apply available Samsung mobile security updates where supported by the device model and carrier.
- Retire or isolate devices that cannot receive relevant security updates.
Validation and detection
- Inventory mobile device model, Android version, chipset, and security patch level.
- Confirm whether each device is within Samsung’s affected software and chipset scope.
- Verify vendor patch status against Samsung’s security update information for SVE-2019-14575.
- Review mobile device management records for unsupported or unpatched affected devices.
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.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-10849 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.