LiveActive security incident?Get immediate response
CVE Record

CVE-2020-3678: u'A buffer overflow could occur if the API is improperly used due to UIE init does not contain a buffer siz...

u'A buffer overflow could occur if the API is improperly used due to UIE init does not contain a buffer size a param' in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in Agatti, Kamorta, QCS404, QCS605, SDA845, SDM670, SDM710, SDM845, SXR1130

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-3678 is a Qualcomm Snapdragon issue where improper use of a UIE initialization API could cause a buffer overflow. The public bundle does not provide severity, CVSS, CWE, exploitability, or a specific patch package, so business urgency depends on whether affected chipsets are present in deployed devices.

Executive priority

Set priority after asset identification. If affected Qualcomm-based devices support critical operations, treat remediation as a firmware lifecycle item requiring vendor confirmation. Without severity or exploitation evidence in the bundle, avoid emergency classification unless internal exposure is high.

Technical view

The CVE describes a buffer overflow condition tied to UIE init lacking a buffer-size parameter when the API is improperly used. Affected Qualcomm platforms include Snapdragon Consumer IoT, Industrial IoT, Mobile, and Wired Infrastructure/Networking products across Agatti, Kamorta, QCS404, QCS605, SDA845, SDM670, SDM710, SDM845, and SXR1130.

Likely exposure

Exposure is most likely in devices, appliances, or embedded products using the listed Qualcomm Snapdragon platforms. This is not described as a conventional application or server vulnerability. Exact exposure depends on OEM firmware, product integration, and whether affected Qualcomm components are reachable in the deployed device.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. It also does not describe public exploit code, attack prerequisites, or remote/local reachability. The only stated condition is improper API use leading to possible buffer overflow.

Researcher notes

Evidence is sparse. The bundle names the vulnerable condition, affected Qualcomm product families, and platform list, but omits CVSS, CWE, attack vector, privileges, patch identifiers, and exploit status. Vendor and OEM bulletin correlation is required for defensible exposure assessment.

Mitigation direction

  • Check Qualcomm's October 2020 bulletin and OEM advisories for applicable firmware guidance.
  • Inventory deployed devices for the listed Snapdragon platforms and chipsets.
  • Apply vendor or OEM firmware/security updates where available.
  • Prioritize critical IoT, mobile, and networking assets using affected chipsets.
  • For unsupported devices, consider compensating controls or replacement planning.

Validation and detection

  • Map asset hardware identifiers to Agatti, Kamorta, QCS404, QCS605, SDA845, SDM670, SDM710, SDM845, or SXR1130.
  • Confirm OEM firmware levels include relevant Qualcomm October 2020 security fixes.
  • Review vendor release notes for explicit CVE-2020-3678 coverage.
  • Check whether affected components exist in production, lab, or spare-device inventories.
  • Document unknown firmware status as residual risk until vendor confirmation is available.
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-3678 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and NetworkingAgatti, Kamorta, QCS404, QCS605, SDA845, SDM670, SDM710, SDM845, 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.