LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11202: Buffer overflow/underflow occurs when typecasting the buffer passed by CPU internally in the library which...

Buffer overflow/underflow occurs when typecasting the buffer passed by CPU internally in the library which is not aligned with the actual size of the structure' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in QCM6125, QCS410, QCS603, QCS605, QCS610, QCS6125, SA6145P, SA6155, SA6155P, SA8155, SA8155P, SDA640, SDA670, SDA845, SDM640, SDM670, SDM710, SDM830, SDM845, SDX50M, SDX55, SDX55M, SM6125, SM6150, SM6150P, SM6250, SM6250P, SM7125, SM7150, SM7150P, SM8150, SM8150P

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11202 is a Qualcomm Snapdragon memory-safety flaw affecting listed Auto, Compute, IoT, Industrial IoT, and Mobile chipsets. The public description indicates a buffer size mismatch during internal processing. Business risk depends on whether your devices use the listed chipsets and whether OEM firmware includes Qualcomm's November 2020 fixes.

Executive priority

Treat this as an inventory-and-patching priority, not a confirmed emergency from the available evidence. Focus first on high-value or hard-to-replace devices using affected Snapdragon platforms.

Technical view

The CVE describes buffer overflow/underflow from typecasting a CPU-provided internal buffer that is not aligned to the actual structure size. Qualcomm lists many Snapdragon chipsets as affected. The bundle provides no CVSS score, CWE, exploitability details, or standalone workaround.

Likely exposure

Exposure is most likely in managed phones, embedded systems, vehicles, gateways, or IoT products built on the listed Snapdragon chipsets. Confirmation requires chipset and firmware inventory plus OEM patch status.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. Check Point research discusses Qualcomm DSP vulnerability research publicly, but that does not establish in-the-wild exploitation for this CVE.

Researcher notes

Available evidence is sparse: affected platforms and a memory corruption description are public, but severity metrics and exploitation prerequisites are absent. Avoid assuming exploitability beyond Qualcomm and Check Point references.

Mitigation direction

  • Review Qualcomm's November 2020 bulletin for this CVE.
  • Apply relevant OEM firmware or security updates for affected devices.
  • Prioritize listed Snapdragon chipsets in managed mobile, IoT, and automotive fleets.
  • If no update exists, request vendor guidance and support timelines.
  • Limit exposure of unpatched devices according to business criticality.

Validation and detection

  • Inventory devices for the affected Snapdragon chipset list.
  • Map each device to OEM firmware and security patch level.
  • Check vendor advisories for CVE-2020-11202 remediation status.
  • Track unsupported devices separately for risk acceptance or replacement.
  • Monitor vendor bulletins for corrected firmware availability.
Prepared
Confidence
medium
Sources
5

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-11202 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
4Source 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon MobileQCM6125, QCS410, QCS603, QCS605, QCS610, QCS6125, SA6145P, SA6155, SA6155P, SA8155, SA8155P, SDA640, SDA670, SDA845, SDM640, SDM670, SDM710, SDM830, SDM845, SDX50M, SDX55, SDX55M, SM6125, SM6150, SM6150P, SM6250, SM6250P, SM7125, SM7150, SM7150P, SM8150, SM8150PListed
Weakness

CWE details

No CWE listed

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