LiveActive security incident?Get immediate response
CVE Record

CVE-2020-3673: u'Buffer overflow can happen as part of SIP message packet processing while storing values in array due to...

u'Buffer overflow can happen as part of SIP message packet processing while storing values in array due to lack of check to validate the index length' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in Agatti, APQ8053, APQ8096AU, APQ8098, Bitra, Kamorta, MSM8905, MSM8909W, MSM8917, MSM8940, MSM8953, MSM8996AU, Nicobar, QCA6390, QCA6574AU, QCM2150, QCS605, QM215, Rennell, SA6155P, SA8155P, Saipan, SDA660, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-3673 is a Qualcomm Snapdragon vulnerability where SIP packet processing can overflow a buffer because array index length was not validated. This could affect Qualcomm-based devices across several Snapdragon product lines. The provided sources do not include CVSS, impact details, or confirmed exploitation.

Executive priority

Treat this as an inventory and firmware-governance issue. Prioritize business-critical Qualcomm-based mobile, IoT, vehicle, or connectivity devices that process SIP traffic, but avoid emergency framing without exploitation or severity evidence.

Technical view

The issue is described as a buffer overflow during SIP message packet processing while storing values in an array without validating index length. Affected Qualcomm Snapdragon platforms include Auto, Compute, Connectivity, Consumer IoT, Industrial IoT, Mobile, and Wearables chipsets listed in the CVE record and Qualcomm bulletin.

Likely exposure

Exposure is most likely in devices using the named Qualcomm chipsets where vendor firmware includes the vulnerable SIP-processing component. Risk depends on OEM integration, firmware version, and whether SIP traffic reaches the affected processing path.

Exploitation context

The bundle does not report active exploitation, and the CVE is not marked KEV. No exploit mechanics, prerequisites, or public proof-of-concept status are provided in the supplied sources.

Researcher notes

Evidence is limited to CVE and Qualcomm bulletin metadata. The supplied bundle lacks CVSS, CWE, detailed impact, patch identifiers, attack vector specifics, and exploit status. Avoid assuming remote code execution or specific products beyond the listed Snapdragon platforms.

Mitigation direction

  • Check Qualcomm's October 2020 bulletin for vendor guidance.
  • Confirm OEM firmware or security updates for affected devices.
  • Prioritize Qualcomm-based systems that process SIP or VoIP traffic.
  • Reduce unnecessary SIP exposure at network boundaries.
  • Track compensating controls until device updates are available.

Validation and detection

  • Inventory devices using the listed Qualcomm chipsets.
  • Map each device to OEM firmware and security bulletin status.
  • Review whether SIP traffic can reach affected devices.
  • Check MDM, EDR, or asset data for firmware patch levels.
  • Monitor for unusual SIP traffic where applicable.
Prepared
Confidence
medium
Sources
3

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-3673 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon WearablesAgatti, APQ8053, APQ8096AU, APQ8098, Bitra, Kamorta, MSM8905, MSM8909W, MSM8917, MSM8940, MSM8953, MSM8996AU, Nicobar, QCA6390, QCA6574AU, QCM2150, QCS605, QM215, Rennell, SA6155P, SA8155P, Saipan, SDA660, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130Listed
Weakness

CWE details

No CWE listed

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