dbcve.org
Apq8017 FirmwareOperating system · Qualcomm

CVE-2020-11293

MEDIUM · 6.0 CVSS v3.1 Published 2021-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Out of bound read can happen in Widevine TA while copying data to buffer from user data due to lack of check of buffer length received in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

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

Out-of-bounds read vulnerability in Widevine Trusted Application across multiple Snapdragon platforms. The vulnerability occurs due to missing buffer length validation when copying data from user input to an internal buffer, allowing unauthorized memory reads beyond buffer boundaries.

MitigationApply vendor-supplied firmware/security updates from Qualcomm and device OEMs that patch the Widevine TA component. Users should ensure devices receive regular security patches.

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
Apq8017 FirmwareOperating system
Affected:all versions
Apq8037 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8064au FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/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 the device chipset model
    Query the system for the SoC/processor identifier using commands such as 'cat /proc/cpuinfo', 'dmesg', or device information APIs (e.g., android.os.Build.HARDWARE on Android). Compare the chipset name against the list: Apq8017, Apq8037, Apq8053, Apq8064au, Apq8096au, Aqt1000, Ar8031, Ar8035.
    Affected if The chipset matches any of the listed affected Qualcomm model numbers.
  2. Confirm Widevine Trusted Application is present
    Check for the presence of the Widevine TA component on the device. On Android this may involve inspecting /vendor/etc/, /system/etc/, or checking DRM service status via 'dumpsys media.drm' or 'getprop ro.widevine.cert'. On other embedded platforms, examine firmware directories or DRM service configurations for Widevine TA files or services.
    Affected if The Widevine TA component is installed or the device advertises Widevine DRM capabilities.
  3. Determine if user input processing is reachable through Widevine
    Assess whether the device processes protected media content through the Widevine DRM pipeline. This can be confirmed by checking if the device can play Widevine-protected streams (e.g., L1 or L3) or by examining active DRM sessions via 'dumpsys media.drm' or equivalent DRM debugging interfaces.
    Affected if The device processes or is capable of processing Widevine-protected content, enabling the attack surface for the vulnerable TA.
  4. Check for installed firmware/security patch level
    Query the installed firmware version and security patch date. On Android this is typically available via 'getprop ro.build.version.security_patch', 'getprop ro.vendor.build.version.security_patch', or in Settings > About Phone > Security Patch Level. For other firmware-based devices, consult vendor-specific diagnostic interfaces or boot logs.
    Affected if The security patch level predates the CVE-2020-11293 fix release date (approximately mid-2020) or the firmware remains at the original vendor version with no documented CVE remediation applied.

A device is affected if it uses any of the listed Qualcomm chipsets (Apq8017, Apq8037, Apq8053, Apq8064au, Apq8096au, Aqt1000, Ar8031, Ar8035) and has the Widevine TA component enabled while running firmware without the CVE-2020-11293 security patch.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware/security updates from Qualcomm and device OEMs that patch the Widevine TA component. Users should ensure devices receive regular security patches.

Fix this in Apq8017 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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