LiveActive security incident?Get immediate response
CVE Record

CVE-2020-3639: u'When a non standard SIP sigcomp message is received from the network, then there may be chances of using...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-3639 concerns Qualcomm Snapdragon platforms processing a non-standard SIP SigComp network message. The issue may consume excessive UDVM cycles or trigger memory overflow. Business urgency depends on whether your fleet includes affected Snapdragon-based mobile, IoT, compute, auto, or wearable devices and whether OEM firmware incorporated Qualcomm's November 2020 guidance.

Executive priority

Treat this as an exposure-mapping and vendor-update item, not a confirmed emergency. Prioritize fleets with Qualcomm-based mobile, IoT, auto, or wearable devices that rely on SIP, IMS, or carrier-managed connectivity, especially where firmware maintenance is slow or outsourced.

Technical view

The CVE describes handling of a non-standard SIP SigComp message received from the network, potentially causing excessive UDVM cycle use or memory overflow. Qualcomm lists many Snapdragon product families and chipsets as affected. The provided sources do not include CVSS, CWE, exploitability details, or precise remediation text beyond the Qualcomm bulletin reference.

Likely exposure

Exposure is most likely in devices using affected Qualcomm Snapdragon chipsets where SIP SigComp processing is reachable through modem, carrier, VoIP, IMS, or similar network paths. Asset owners may need OEM or carrier mapping because Qualcomm chipsets are embedded inside finished products.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. It only states that a non-standard SIP SigComp message received from the network may lead to excessive UDVM cycle use or memory overflow. No public exploit details are provided in the supplied evidence.

Researcher notes

Evidence is thin: no CVSS, CWE, patch detail, or exploit status is included in the provided bundle. Analysis should stay anchored to Qualcomm's advisory and CVE text. The key research task is product-to-chipset mapping and confirming whether reachable SIP SigComp handling exists in deployed firmware.

Mitigation direction

  • Check Qualcomm's November 2020 security bulletin for vendor guidance.
  • Confirm OEM or carrier firmware updates for affected device models.
  • Apply available vendor firmware or security updates after compatibility testing.
  • Limit SIP or IMS signaling exposure to trusted network paths where feasible.
  • Monitor affected device classes for abnormal modem or SIP processing failures.

Validation and detection

  • Inventory devices using the listed Qualcomm Snapdragon chipsets.
  • Map chipset exposure to finished product models and firmware versions.
  • Compare firmware levels against Qualcomm and OEM November 2020 advisory status.
  • Confirm whether SIP SigComp processing is enabled or reachable.
  • Track unresolved devices requiring OEM, carrier, or vendor confirmation.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-3639 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon WearablesAPQ8009, 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, SXR1130Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.