dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2020-3639

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-12
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
u'When a non standard SIP sigcomp message is received from the network, then there may be chances of using more UDVM cycle or memory overflow' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8009, APQ8017, APQ8037, APQ8053, MDM9250, MDM9607, MDM9628, MDM9640, MDM9650, MSM8108, MSM8208, MSM8209, MSM8608, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, QCM4290, QCM6125, QCS410, QCS4290, QCS603, QCS605, QCS610, QCS6125, QM215, QSM8350, SA415M, SA6145P, SA6150P, SA6155P, SA8150P, SA8155, SA8155P, SA8195P, SC7180, SC8180X, SC8180X+SDX55, SC8180XP, SDA429W, SDA640, SDA660, SDA670, SDA845, SDA855, SDM1000, SDM429, SDM429W, SDM439, SDM450, SDM455, SDM630, SDM632, SDM636, SDM640, SDM660, SDM670, SDM710, SDM712, SDM845, SDM850, SDX24, SDX50M, SDX55, SDX55M, SM4125, SM4250, SM4250P, SM6115, SM6115P, SM6125, SM6150, SM6150P, SM6250, SM6250P, SM7125, SM7150, SM7150P, SM7250, SM7250P, SM8150, SM8150P, SM8350, SM8350P, SXR1120, 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' SigComp (Signaling Compression) implementation for SIP messages. When a malformed or non-standard SIP sigcomp message is received from the network, it can cause excessive UDVM (Universal Decompressor Virtual Machine) cycle consumption or trigger a memory overflow condition. This can lead to denial of service or potentially remote code execution. The vulnerability is remotely exploitable via network traffic without authentication.

MitigationApply vendor-provided security patches from Qualcomm and device OEMs. This is a firmware-level vulnerability that requires updating the processor firmware/baseband processor. For organizations, identify and inventory all affected devices and apply available security updates from device manufacturers.

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
Apq8037 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Mdm9250 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9628 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Inventory device chipset models
    Identify all network-connected devices and determine their Qualcomm processor model numbers (Apq8009, Apq8017, Apq8037, Apq8053, Mdm9250, Mdm9607, Mdm9628, Mdm9640) by reviewing device specifications, baseband firmware diagnostics, or SNMP/network inventory data
    Affected if Any device is found using one of the affected chipset models listed in the CVE
  2. Check baseband firmware version
    Query the baseband processor firmware version on identified Qualcomm devices using manufacturer diagnostic tools, AT commands (for modems), or device management interfaces. Compare the version against any available patch releases from Qualcomm or OEM vendors
    Affected if The firmware version is older than available patches or, for 'all versions' products, no patch has been applied
  3. Identify SIP/SigComp exposure
    Determine whether SIP-based voice or messaging services are enabled and whether the SigComp compression feature is active on the device or network edge. Review VoIP/SIP server configurations, SIP proxy settings, and any SigComp-related parameters
    Affected if SIP services with SigComp compression are enabled and exposed to network traffic
  4. Monitor for malformed SIP sigcomp messages
    Capture and inspect network traffic on SIP ports (typically 5060/5061) for SIP messages containing SigComp compressed bodies. Look for anomalies in the UDVM bytecode, unusual decompression behavior, or messages that trigger excessive processing
    Affected if Malformed or anomalous SIP sigcomp messages are observed in network captures, or unexpected UDVM cycle consumption is detected on SIP-processing systems

A defender is affected if their environment contains devices using any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8037, Apq8053, Mdm9250, Mdm9607, Mdm9628, Mdm9640) that have not been patched, and those devices process SIP traffic with SigComp enabled.

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 security patches from Qualcomm and device OEMs. This is a firmware-level vulnerability that requires updating the processor firmware/baseband processor. For organizations, identify and inventory all affected devices and apply available security updates from device manufacturers.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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