dbcve.org
Apq8017 FirmwareOperating system · Qualcomm

CVE-2020-11247

CRITICAL · 9.1 CVSS v3.1 Published 2021-04-07
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
Out of bound memory read while unpacking data due to lack of offset length check in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

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

An out-of-bounds memory read vulnerability in Qualcomm Snapdragon chipset firmware allows attackers to read sensitive memory contents due to missing offset and length validation during data unpacking operations. This affects multiple Snapdragon product lines including mobile, IoT, automotive, compute, and wearable platforms.

MitigationApply vendor-supplied firmware updates for affected Snapdragon devices; contact device manufacturers for patch availability and deployment schedules.

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
Aqt1000 FirmwareOperating system
Affected:all versions
Msm8917 FirmwareOperating system
Affected:all versions
Msm8920 FirmwareOperating system
Affected:all versions
Msm8937 FirmwareOperating system
Affected:all versions
Msm8940 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 your device chipset model
    On Android, check /proc/cpuinfo or use 'lscpu' command; on Linux embedded systems, check /proc/cpuinfo or dmesg for Qualcomm Snapdragon identifiers. Look for APQ or MSM model numbers such as APQ8017, APQ8037, APQ8053, AQT1000, MSM8917, MSM8920, MSM8937, or MSM8940.
    Affected if The chipset model matches one of the affected identifiers: APQ8017, APQ8037, APQ8053, AQT1000, MSM8917, MSM8920, MSM8937, or MSM8940.
  2. Check baseband or firmware version
    On Android, go to Settings > About Phone > Build Number, or check /proc/version, or use 'getprop' commands (getprop ro.build.fingerprint, getprop gsm.version.baseband). For IoT/embedded devices, consult vendor documentation or check /proc/cmdline for boot parameters indicating firmware version.
    Affected if Any firmware version is present on an affected chipset model, since the advisory states all versions are affected.
  3. Confirm the vulnerability trigger condition
    This is a firmware-level flaw in data unpacking operations within the baseband processor or system-on-chip firmware. The vulnerability exists in the modem/baseband subsystem handling packed data protocols. To confirm exposure, verify that the device uses the affected Snapdragon chipset and that baseband firmware is active and accessible to untrusted data inputs.
    Affected if The device runs on an affected Snapdragon chipset (APQ or MSM series listed) and processes external packed data through the baseband or firmware data handling routines.

A device is affected if it contains any of the listed Qualcomm Snapdragon chipset models (APQ8017, APQ8037, APQ8053, AQT1000, MSM8917, MSM8920, MSM8937, MSM8940) regardless of firmware version, as all versions of the affected firmware are vulnerable to the out-of-bounds read during data unpacking.

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 updates for affected Snapdragon devices; contact device manufacturers for patch availability and deployment schedules.

Fix this in Apq8017 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA16.0 h
88.0 hours of engineering $15,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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