LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25051: An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) software.

An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) software. Attackers can bypass Factory Reset Protection (FRP) via AppInfo. The Samsung ID is SVE-2020-17758 (August 2020).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-25051 describes a Factory Reset Protection bypass on Samsung mobile devices running Android P (9.0) or Q (10.0). FRP is intended to reduce misuse of lost or stolen devices after reset. The public record is sparse and does not provide CVSS, CWE, or detailed model coverage.

Executive priority

Treat this as a legacy mobile fleet control issue, not a confirmed active exploitation emergency. Prioritize organizations with managed Samsung Android 9 or 10 devices, especially where lost or stolen device risk is material.

Technical view

The issue is identified by Samsung as SVE-2020-17758 in the August 2020 update context. The CVE states attackers can bypass FRP via AppInfo on Samsung mobile devices with P and Q software. No exploit details, patch matrix, or precise affected CPEs are provided in the source bundle.

Likely exposure

Exposure appears limited to Samsung mobile devices running Android 9.0 or 10.0 where the relevant Samsung security update is absent. The sources do not identify exact models, regions, carriers, or build numbers.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The CVE describes the bypass class but does not include exploitation prevalence, proof-of-concept status, or attack prerequisites.

Researcher notes

Evidence is incomplete. The CVE record provides the FRP bypass vector and Samsung identifier, but no CVSS, CWE, CPEs, affected model list, exploit status, or detailed remediation text beyond the Samsung security update reference.

Mitigation direction

  • Check Samsung guidance for SVE-2020-17758 and applicable August 2020 security updates.
  • Apply supported Samsung security updates to affected Android 9.0 and 10.0 devices.
  • Use MDM compliance rules to flag outdated Samsung security patch levels.
  • Retire or restrict devices that cannot receive relevant vendor updates.

Validation and detection

  • Inventory Samsung devices running Android P (9.0) or Q (10.0).
  • Verify each device security patch level against Samsung’s SVE-2020-17758 guidance.
  • Confirm MDM reports cover Android version, model, and patch level.
  • Review lost-device and decommissioning workflows that rely on FRP.
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-25051 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.