dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2020-3624

HIGH · 7.8 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 →
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
u'A potential buffer overflow exists due to integer overflow when parsing handler options due to wrong data type usage in operation' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, Kamorta, MDM9150, MDM9205, MDM9206, MDM9207C, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8905, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCM2150, QCN7605, QCS605, QCS610, QM215, Rennell, SA415M, SA515M, Saipan, SC7180, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SDX55, 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

A buffer overflow vulnerability exists in Qualcomm Snapdragon processors caused by an integer overflow when parsing handler options. The issue stems from incorrect data type usage in a specific operation, allowing an attacker to overflow a buffer and potentially execute arbitrary code or cause denial of service.

MitigationApply vendor-provided firmware/security patches from Qualcomm and device manufacturers. Since this is a hardware/firmware-level issue, organizations should inventory affected devices, verify patch availability from OEMs, and prioritize patching based on exposure and criticality.

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
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Kamorta FirmwareOperating system
Affected:all versions
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9205 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 the Qualcomm chipset model
    Check the device specifications, system information, or hardware inventory to determine if the chipset is one of: Apq8009, Apq8017, Apq8053, Apq8096au, Apq8098, Kamorta, Mdm9150, or Mdm9205
    Affected if The device uses any of the listed Qualcomm chipset models
  2. Determine the firmware version
    Access the device firmware information through manufacturer diagnostic tools, bootloader information, or system firmware revision settings. Query the baseband processor or radio firmware version if available.
    Affected if The firmware version is any version (all versions are affected according to the advisory)
  3. Verify handler options parsing is enabled
    Identify if the specific handler options parsing module is active on the device. This may require access to firmware debugging interfaces or examining the baseband/radio firmware configuration.
    Affected if The handler options parsing feature is present and operational in the firmware
  4. Check for known vendor patches
    Consult the device manufacturer or Qualcomm advisory to determine if a firmware security update addressing CVE-2020-3624 has been released and applied.
    Affected if No vendor security patch for CVE-2020-3624 has been applied to the device firmware

A device is affected if it utilizes any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8096au, Apq8098, Kamorta, Mdm9150, Mdm9205) and does not have a vendor-supplied firmware patch for this specific 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

Apply vendor-provided firmware/security patches from Qualcomm and device manufacturers. Since this is a hardware/firmware-level issue, organizations should inventory affected devices, verify patch availability from OEMs, and prioritize patching based on exposure and criticality.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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