LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10839: An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) software.

An issue was discovered on Samsung mobile devices with O(8.x), P(9.0), and Q(10.0) software. Attackers can bypass Factory Reset Protection (FRP) via a SIM card. The Samsung ID is SVE-2019-16193 (February 2020).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-10839 is a Samsung mobile device issue where Factory Reset Protection can be bypassed using a SIM card. FRP is intended to deter unauthorized reuse after reset, so exposure mainly concerns lost, stolen, resold, or decommissioned devices running Android O, P, or Q-era Samsung software.

Executive priority

Treat this as an asset hygiene and mobile fleet control issue unless vendor or threat intelligence shows active abuse. Prioritize older Samsung devices that remain in use, are unmanaged, or may be resold or lost.

Technical view

The CVE describes an FRP bypass on Samsung devices with O(8.x), P(9.0), and Q(10.0) software. Samsung tracks it as SVE-2019-16193 in the February 2020 security update. The source bundle provides no CVSS, CWE, root cause, exploit prerequisites, or detailed patch instructions.

Likely exposure

Potentially exposed assets are Samsung mobile devices on Android 8.x, 9.0, or 10.0 software that have not received the relevant Samsung February 2020 security update or later vendor guidance.

Exploitation context

The bundle states bypass is possible via a SIM card, but does not document active exploitation, public exploit availability, required access level, or attack complexity. It is not listed as CISA KEV in the provided data.

Researcher notes

Evidence is sparse. The CVE gives the affected Android generations, FRP bypass class, SIM-card vector, and Samsung advisory identifier only. Do not assume data access, remote exploitation, or a specific fix beyond checking Samsung guidance.

Mitigation direction

  • Identify Samsung devices running Android 8.x, 9.0, or 10.0 software.
  • Check Samsung’s February 2020 security update guidance for SVE-2019-16193.
  • Apply applicable Samsung firmware/security updates through managed update channels.
  • Retire or isolate devices that cannot receive relevant vendor updates.
  • Strengthen lost-device and decommissioning controls in MDM workflows.

Validation and detection

  • Inventory Samsung model, Android version, and security patch level across managed devices.
  • Confirm whether each device received Samsung’s February 2020 security update or later.
  • Review MDM records for stale, unmanaged, lost, or decommissioned Samsung devices.
  • Check asset disposal procedures for reset, ownership transfer, and FRP handling evidence.
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-2020-10839 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.