LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11130: u'Possible buffer overflow in WIFI hal process due to copying data without checking the buffer length' in S...

u'Possible buffer overflow in WIFI hal process due to copying data without checking the buffer length' in Snapdragon Auto, Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile in QCM4290, QCS4290, QM215, QSM8350, SA6145P, SA6155, SA6155P, SA8155, SA8155P, SC8180X, SC8180XP, SDX55, SDX55M, SM4250, SM4250P, SM6115, SM6115P, SM6125, SM6250, SM6350, SM7125, SM7225, SM7250, SM7250P, SM8150, SM8150P, SM8250, SM8350, SM8350P, SXR2130, SXR2130P

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11130 is a Qualcomm Snapdragon Wi-Fi HAL buffer overflow issue. In affected devices, Wi-Fi-related firmware/software may copy data without validating buffer length. The public bundle does not provide CVSS, exact impact, exploitability, or confirmed patch details, so business urgency depends on affected chipset presence and OEM firmware status.

Executive priority

Treat this as an asset-identification and supplier-follow-up item. Escalate for automotive, industrial IoT, and mobile fleets using listed Snapdragon platforms, but avoid emergency framing unless vendor guidance or internal validation confirms exploitable exposure.

Technical view

The CVE describes a possible buffer overflow in the Wi-Fi HAL process caused by unchecked data copying. Affected Qualcomm platforms include Snapdragon Auto, Compute, Industrial IoT, and Mobile chipsets listed in the record. The source bundle does not identify CWE, CPEs, attack vector, privileges required, or impact scope.

Likely exposure

Exposure is most likely for organizations operating products or fleets built on the listed Snapdragon chipsets. Risk depends on whether the device uses the affected Qualcomm Wi-Fi HAL implementation and whether OEM firmware updates have addressed the issue.

Exploitation context

The provided sources do not indicate active exploitation, and the CVE is not marked as KEV in the bundle. No exploit status, proof of concept, or attacker prerequisites are provided, so exploitation likelihood cannot be assessed from this evidence alone.

Researcher notes

The record gives root cause and affected chipsets but omits CVSS, CWE, CPEs, fixed versions, and exploit prerequisites. Validation should focus on chipset mapping, firmware provenance, and OEM bulletin correlation rather than assumptions about reachability or impact.

Mitigation direction

  • Check Qualcomm’s November 2020 bulletin for vendor guidance.
  • Request affected firmware status from device OEMs or suppliers.
  • Apply OEM security firmware updates when available.
  • Prioritize managed devices using the listed Snapdragon chipsets.
  • Track unresolved devices in vulnerability management exceptions.

Validation and detection

  • Inventory devices by Snapdragon chipset or platform identifier.
  • Compare discovered chipsets against the affected list.
  • Check OEM firmware versions against vendor security advisories.
  • Confirm whether Wi-Fi HAL components came from affected Qualcomm releases.
  • Document devices lacking OEM patch confirmation.
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-11130 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 Industrial IOT, Snapdragon MobileQCM4290, QCS4290, QM215, QSM8350, SA6145P, SA6155, SA6155P, SA8155, SA8155P, SC8180X, SC8180XP, SDX55, SDX55M, SM4250, SM4250P, SM6115, SM6115P, SM6125, SM6250, SM6350, SM7125, SM7225, SM7250, SM7250P, SM8150, SM8150P, SM8250, SM8350, SM8350P, SXR2130, SXR2130PListed
Weakness

CWE details

No CWE listed

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