CVE-2020-25051
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability allows attackers to bypass Factory Reset Protection (FRP) on Samsung mobile devices running Android P (9.0) and Q (10.0) by exploiting the AppInfo component. FRP is designed to prevent unauthorized access after a factory reset, so bypassing it enables use of stolen devices.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 9.0= 10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device manufacturer and modelCheck the device settings to confirm it is a Samsung mobile device. Go to Settings > About Phone > Model Number.Affected if The device is not a Samsung product - this vulnerability only affects Samsung devices.
-
Check the Android OS versionGo to Settings > About Phone > Android Version. Confirm whether the installed version is 9.0 or 10.0.Affected if The device is running Android 9.0 or 10.0 exactly as listed in the affected versions.
-
Verify the Samsung security patch levelGo to Settings > About Phone > Security Patch Level. Compare the displayed date against Samsung's security bulletins for the month the fix was released.Affected if The Security Patch Level is earlier than the Samsung security update that addresses this AppInfo FRP bypass vulnerability.
-
Confirm FRP protection statusFactory reset the device (in a safe test environment) and observe whether the setup wizard properly enforces Factory Reset Protection login requirements.Affected if FRP is not properly enforced after a factory reset - the bypass allows unauthorized access.
The device is affected if it is a Samsung mobile device running Android 9.0 or 10.0 and has not received the Samsung security patch that addresses the AppInfo FRP bypass vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSamsung should release a security patch addressing the AppInfo FRP bypass. Users should apply the latest Samsung security updates. Enterprise MDM solutions may need to reassess device security policies for affected OS versions.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-25051 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data