dbcve.org
AndroidOperating system · Google

CVE-2020-13832

CRITICAL · 9.8 CVSS v3.1 Published 2020-06-04
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) (with TEEGRIS on Exynos chipsets) software. The Widevine Trustlet allows arbitrary code execution because of memory disclosure, The Samsung IDs are SVE-2020-17117, SVE-2020-17118, SVE-2020-17119, and SVE-2020-17161 (June 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 · high confidence

The Widevine Trustlet on Samsung mobile devices with Q(10.0) and TEEGRIS on Exynos chipsets contains a memory disclosure vulnerability that allows arbitrary code execution in the Trusted Execution Environment (TEE). An attacker can read arbitrary memory locations within the trustlet, which can be leveraged to achieve code execution in this privileged secure context.

MitigationUsers must obtain and apply the Samsung firmware update addressing SVE-2020-17117 through SVE-2020-17161. Since this is a TEE firmware vulnerability, no user-facing configuration changes can remediate it; device firmware must be patched by Samsung.

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. Identify device manufacturer and chipset
    Check if the device is a Samsung mobile device and verify the chipset is Exynos (not Qualcomm Snapdragon). On Android, this can be done by checking 'Settings > About Phone > Model' and either checking 'Settings > About Phone > Baseband version' or using a terminal app with 'cat /proc/cpuinfo' to see the processor details.
    Affected if The device is a Samsung mobile device running on an Exynos chipset.
  2. Verify Android version is 10.0
    Check the Android version by going to 'Settings > About Phone > Android version' or using 'adb shell getprop ro.build.version.release' via ADB. Confirm the version is exactly 10.0 (Q).
    Affected if Android version is 10.0 (build version release shows 10).
  3. Confirm TEEGRIS TEE is in use
    This vulnerability affects Samsung's TEEGRIS (the TEE implementation on Exynos-based Samsung devices). Check via 'adb shell teegrinsd -v' or examine TEE info via 'adb shell dmesg | grep -i tee' to see if TEEGRIS is listed as the active TEE.
    Affected if TEEGRIS is identified as the Trusted Execution Environment in use.
  4. Verify Widevine DRM is present
    Confirm Widevine support exists on the device by checking 'Settings > Google > DRM Info' or using a DRM info app. Widevine is typically present on all devices that support streaming services.
    Affected if Widevine DRM is present on the device (this is a Widevine Trustlet vulnerability).

If the device is a Samsung mobile phone with an Exynos chipset running Android 10.0 and uses TEEGRIS with Widevine DRM, then the environment is affected by this vulnerability.

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

Users must obtain and apply the Samsung firmware update addressing SVE-2020-17117 through SVE-2020-17161. Since this is a TEE firmware vulnerability, no user-facing configuration changes can remediate it; device firmware must be patched by Samsung.

Recommended fix Moderate confidence

Android 11 or later (contains fixed Widevine Trustlet)

  1. Check your device model against Samsung's June 2020 security bulletin (SVE-2020-17117, SVE-2020-17118, SVE-2020-17119, SVE-2020-17161) at security.samsungmobile.com to confirm if your specific Exynos chipset device with TEEGRIS is affected
  2. Apply the June 2020 security patch or later via Settings > Security > Security update on your Samsung device
  3. If available, upgrade to Android 11 or later which contains the fixed TEEGRIS/Widevine Trustlet implementation
  4. Verify the patch was applied by checking Settings > About phone > Software information > Security patch level
Caveat Upgrading to Android 11 may remove support for some legacy apps or device-specific features; verify app compatibility before upgrading

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
2.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-13832 — 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-13832 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