LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11190: Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP...

Buffer over-read can happen while parsing received SDP values due to lack of NULL termination check on SDP in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Qualcomm issue can make affected Snapdragon-based products read beyond intended memory while parsing received SDP values. The public bundle does not state impact, CVSS severity, or whether data leakage or crash is possible. Treat it as an exposure-management item for products using the listed Snapdragon platforms, especially embedded, mobile, IoT, automotive, and wearable fleets.

Executive priority

Medium tracking priority until exposure is confirmed. The affected product scope is broad, but the public evidence lacks severity, impact, and exploitation details. Focus on identifying affected devices and obtaining OEM remediation status rather than emergency response.

Technical view

CVE-2020-11190 is a buffer over-read caused by missing NULL-termination checks when parsing received SDP values. Qualcomm lists many Snapdragon product families and component identifiers as affected. The provided data does not include CWE, CVSS, patch details, proof-of-concept status, or precise vulnerable firmware versions beyond the listed platforms.

Likely exposure

Exposure is likely in devices using affected Qualcomm Snapdragon Auto, Compute, Connectivity, IoT, Mobile, Voice & Music, or Wearables components. Organizations may need OEM bills of materials, firmware inventories, or vendor attestations because chipset-level CVEs are often hidden behind device model names.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked CISA KEV. No exploit method or public exploit evidence is included. The only technical context provided is malformed or unexpected received SDP values triggering a parser buffer over-read condition.

Researcher notes

Evidence is thin: the bundle gives the bug class, parser context, affected Qualcomm families, and bulletin link, but not vulnerable code paths, CVSS, impact, or fix identifiers. Avoid assuming Bluetooth, remote code execution, information disclosure, or crash impact without additional vendor evidence.

Mitigation direction

  • Review Qualcomm's March 2021 security bulletin for vendor guidance.
  • Ask device OEMs for firmware status against CVE-2020-11190.
  • Prioritize updates for internet-exposed, mobile, IoT, and operational devices.
  • Restrict unnecessary interfaces that process received SDP data where feasible.
  • Track compensating controls when OEM patches are unavailable.

Validation and detection

  • Inventory devices using affected Qualcomm Snapdragon platforms or listed components.
  • Map device models to chipset and firmware versions with OEM support data.
  • Check OEM advisories for CVE-2020-11190 remediation statements.
  • Confirm deployed firmware includes the relevant Qualcomm security bulletin fixes.
  • Document exceptions where vendors provide no remediation information.
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-11190 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 IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon WearablesAPQ8009, APQ8009W, APQ8017, APQ8037, APQ8053, APQ8084, APQ8096AU, AQT1000, AR8035, AR8151, CSR6030, CSRB31024, MDM8207, MDM9150, MDM9205, MDM9206, MDM9207, MDM9250, MDM9607, MDM9628, MDM9640, MDM9645, MDM9650, MDM9655, MSM8108, MSM8208, MSM8209, MSM8608, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8976, MSM8976SG, MSM8996AU, PM215, PM3003A, PM4125, PM4250, PM439, PM456, PM6125, PM6150, PM6150A, PM6150L, PM6250, PM640A, PM640L, PM640P, PM660, PM660A, PM660L, PM670, PM670L, PM7150A, PM7150L, PM7250, PM7250B, PM8004, PM8005, PM8008, PM8009, PM8150, PM8150A, PM8150B, PM8150C, PM8150L, PM8250, PM855, PM855A, PM855B, PM855L, PM855P, PM8909, PM8916, PM8937, PM8940, PM8952, PM8953, PM8956, PM8996, PM8998, PMC1000H, PMD9607, PMD9645, PMD9655, PMD9655AU, PME605, PMI632, PMI8937, PMI8940, PMI8952, PMI8994, PMI8996, PMI8998, PMK8001, PMK8002, PMM855AU, PMM8996AU, PMR525, PMR735A, PMW3100, PMX20, PMX24, PMX50, PMX55, QAT3514, QAT3516, QAT3518, QAT3519, QAT3522, QAT3550, QAT3555, QAT5515, QAT5 ...[truncated*]Listed
Weakness

CWE details

No CWE listed

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