dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2020-3619

HIGH · 7.0 CVSS v3.1 Published 2020-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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
u'Non-secure memory is touched multiple times during TrustZone\u2019s execution and can lead to privilege escalation or memory corruption' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8098, IPQ8074, Kamorta, MDM9150, MDM9206, MDM9607, MDM9650, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8998, QCA8081, QCS404, QCS605, QCS610, QM215, Rennell, SA415M, SC7180, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX24, SM6150, SM7150, SM8150, SXR1130

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

Vulnerability in Qualcomm Snapdragon chips where non-secure memory is improperly accessed multiple times during TrustZone execution. TrustZone is ARM's trusted execution environment meant to isolate secure operations from the normal world; touching non-secure memory breaks this isolation boundary and can enable privilege escalation from the secure world or memory corruption attacks.

MitigationThis is a firmware/hardware vulnerability requiring patch deployment through the chip vendor (Qualcomm) to device manufacturers, then OTA updates to end devices. Organizations should identify affected devices in their inventory and monitor for vendor firmware releases.

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
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Ipq8074 FirmwareOperating system
Affected:all versions
Kamorta FirmwareOperating system
Affected:all versions
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9206 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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 devices with Qualcomm Snapdragon chips
    Review hardware inventory, device manifests, or use system information tools (like 'lspci', 'lsusb', or device management consoles) to list embedded modem or processor chips in endpoints, IoT devices, or network equipment
    Affected if Any device contains a Qualcomm Snapdragon, Snapdragon Wear, or cellular modem chip from the product line
  2. Determine the specific chip model number
    Extract the exact Qualcomm part number from device specifications, firmware strings, or diagnostic outputs (e.g., 'AT+CGMM' for modems, boot logs, or hardware BOMs)
    Affected if The chip model matches one of: Apq8009, Apq8017, Apq8053, Apq8098, Ipq8074, Kamorta, Mdm9150, or Mdm9206
  3. Retrieve the current firmware version
    Query the firmware version through vendor-specific interfaces (AT commands for modems, diag ports, debug logs, or device management APIs)
    Affected if Firmware is present on any of the affected chip models listed (the CVE states all versions are affected)
  4. Confirm TrustZone/TEE is in use
    Check if the device utilizes ARM TrustZone or a Trusted Execution Environment by reviewing secure boot configuration, TEE driver presence (/dev/tee*, tee-supplicant), or vendor documentation
    Affected if TrustZone is enabled and the chip is on the affected list (the vulnerability exploits TrustZone memory access)

If devices in your environment contain any of the listed Qualcomm chip models (Apq8009, Apq8017, Apq8053, Apq8098, Ipq8074, Kamorta, Mdm9150, Mdm9206) and run their firmware, 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.

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

This is a firmware/hardware vulnerability requiring patch deployment through the chip vendor (Qualcomm) to device manufacturers, then OTA updates to end devices. Organizations should identify affected devices in their inventory and monitor for vendor firmware releases.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation40.0 h
  • Testing80.0 h
  • Review / QA24.0 h
144.0 hours of engineering $24,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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