dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2020-3665

HIGH · 7.8 CVSS v3.1 Published 2020-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
A possible buffer overflow would occur while processing command from firmware due to the group_id obtained from the firmware being out of range in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8009, APQ8053, APQ8096AU, MDM9206, MDM9207C, MDM9607, MDM9615, MDM9640, MDM9650, MSM8909W, MSM8996, MSM8996AU, QCA6174A, QCA9377, QCA9379, SDM439, SDM636, SDM660, SDX20, SDX24, SM8150

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

A buffer overflow vulnerability exists in Qualcomm Snapdragon firmware where an out-of-range group_id value is not properly validated before being used in memory operations. When processing commands from firmware, the unchecked group_id can lead to memory corruption and potential code execution.

MitigationApply firmware updates provided by Qualcomm to affected device manufacturers. Organizations should identify and inventory all affected Snapdragon-based devices in their environment and work with OEMs/vendors to deploy the patched firmware.

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
Apq8009 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9207c FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9615 FirmwareOperating system
Affected:all versions
Mdm9640 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 hardware using affected Qualcomm chipsets
    Review device inventory, hardware specifications, or system information to determine if any devices contain the following Qualcomm chipsets: Apq8009, Apq8053, Apq8096au, Mdm9206, Mdm9207c, Mdm9607, Mdm9615, or Mdm9640. This may require checking device datasheets, BOM (Bill of Materials) documents, or using diagnostic tools that report chipset information.
    Affected if Any device in the environment uses one of the listed Qualcomm chipsets
  2. Locate firmware version for the chipset
    Access the device firmware or boot ROM information. On affected devices, this is typically found in: bootloader diagnostics, /proc/bootinfo, or by querying the baseband processor firmware version through AT commands (for modems) or through vendor-specific diagnostic interfaces. Compare the firmware version against any patched releases provided by the device OEM.
    Affected if Firmware version cannot be confirmed as patched or the device vendor has not released a CVE-2020-3665 patch
  3. Verify command processing from firmware is active
    Determine if the device actively processes commands from the Qualcomm firmware component that handles group_id validation. This is typically always active on affected chipsets as it relates to baseband/modem firmware operations. Check if the device uses the Snapdragon modem or application processor firmware stacks.
    Affected if The device utilizes the firmware component that processes group_id values in memory operations (inherent to the listed chipsets)

If any device in the environment uses one of the eight listed Qualcomm chipsets (Apq8009, Apq8053, Apq8096au, Mdm9206, Mdm9207c, Mdm9607, Mdm9615, Mdm9640) and the OEM has not confirmed a firmware patch for CVE-2020-3665, the environment is affected.

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 firmware updates provided by Qualcomm to affected device manufacturers. Organizations should identify and inventory all affected Snapdragon-based devices in their environment and work with OEMs/vendors to deploy the patched firmware.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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