CVE-2020-12745
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 Q(10.0) software. Attackers can bypass the locked-state protection mechanism and access clipboard content via USSD. The Samsung ID is SVE-2019-16556 (May 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 in Samsung mobile devices running Android Q (10.0) allows attackers to bypass the locked-state protection mechanism and access clipboard content via USSD (Unstructured Supplementary Service Data). The issue stems from a failure to properly enforce lock-screen protections when processing USSD requests, enabling unauthorized clipboard data exposure.
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= 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 device manufacturerCheck if the device is made by Samsung. On most Android devices, go to Settings > About Phone > Manufacturer or check the device model number.Affected if Device is not Samsung - the vulnerability specifically affects Samsung mobile devices only.
-
Verify Android version is 10.0Go to Settings > About Phone > Android version. Confirm the version displays exactly 10.0 or Android Q.Affected if Android version is not 10.0 - only Android Q (10.0) is affected by this specific CVE.
-
Check security patch levelGo to Settings > About Phone > Security patch level. This displays the date of the installed Android security update.Affected if Security patch level is earlier than May 2020 - the fix (SVE-2019-16556) was released in Samsung's May 2020 security patch.
-
Confirm USSD accessibility behaviorWhile the screen is locked (with PIN/pattern/password), attempt to trigger a USSD code via the phone dialer. Observe if clipboard content can be accessed or exposed through the USSD response.Affected if USSD requests return clipboard data or sensitive information without requiring device unlock - indicates the lock-screen bypass is present.
A Samsung device running Android 10.0 with a security patch level earlier than May 2020 is likely affected if USSD codes can access clipboard content while the screen is locked.
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 dataApply Samsung's May 2020 security patch (SVE-2019-16556) to affected devices. Until patched, avoid leaving sensitive data in the clipboard and consider additional screen-lock timeout settings.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12745 — 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-12745 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