dbcve.org
AndroidOperating system · Google

CVE-2020-11600

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered on Samsung mobile devices with Q(10.0) software. There is arbitrary code execution in the Fingerprint Trustlet via a memory overwrite. The Samsung IDs are SVE-2019-16587, SVE-2019-16588, SVE-2019-16589 (April 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 confidence

A memory overwrite vulnerability in the Fingerprint Trustlet on Samsung mobile devices running Android Q (10.0) allows arbitrary code execution. The Trustlet is a trusted application that handles fingerprint authentication in the secure execution environment, and the memory corruption enables attackers to execute code with elevated privileges outside the normal OS.

MitigationApply Samsung's April 2020 security patches (SVE-2019-16587, SVE-2019-16588, SVE-2019-16589) to affected devices. For enterprise deployments, verify all fleet devices have received the Q (10.0) security update and consider restricting biometric authentication to trusted applications until patched.

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
AndroidOperating system
Affected:= 10.0

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version is exactly 10.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if Android version shows 10.0 (Android Q) - versions other than 10.0 are not affected by this specific CVE
  2. Confirm device is a Samsung model
    Check Settings > About Phone > Model number, or run 'getprop ro.product.manufacturer' and 'getprop ro.product.model' via ADB
    Affected if The device is manufactured by Samsung; this vulnerability exists in Samsung's Fingerprint Trustlet implementation
  3. Check the installed security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB
    Affected if Security patch level is earlier than April 2020; versions dated April 2020 or later include the fix for SVE-2019-16587, SVE-2019-16588, SVE-2019-16589
  4. Verify fingerprint authentication is enrolled
    Go to Settings > Biometrics and security > Fingerprints, or check if /data/system_fingerprint/ directory exists
    Affected if Fingerprint is enrolled and the Fingerprint Trustlet is active; the vulnerability only triggers when fingerprint authentication is configured on the device

The device is affected if it is a Samsung device running Android 10.0 with a security patch level before April 2020 and has fingerprint authentication enrolled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Samsung's April 2020 security patches (SVE-2019-16587, SVE-2019-16588, SVE-2019-16589) to affected devices. For enterprise deployments, verify all fleet devices have received the Q (10.0) security update and consider restricting biometric authentication to trusted applications until patched.

Recommended fix High confidence

Apply Samsung security patch released April 2020 or later (SVE-2019-16587, SVE-2019-16588, SVE-2019-16589)

  1. Go to Settings > About Phone on the Samsung device
  2. Tap on Software Update
  3. Tap on Download and Install to apply the latest Samsung security patch
  4. Ensure the device is connected to Wi-Fi and charged during the update process
  5. After update completes, verify the security patch level in Settings > About Phone > Software Information > Security patch level shows April 2020 or later
Caveat Standard security update; minimal risk. Ensure device has >50% battery before updating.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11600 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-11600 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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