LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11166: Potential out of bound read exception when UE receives unusually large number of padding octets in the begi...

Potential out of bound read exception when UE receives unusually large number of padding octets in the beginning of ROHC header 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

CVE-2020-11166 is a Qualcomm Snapdragon issue where specially unusual ROHC header padding could cause an out-of-bounds read exception in user equipment. The provided sources do not give a CVSS score, confirmed impact beyond an exception, or active exploitation evidence.

Executive priority

Treat this as a firmware supply-chain exposure requiring asset mapping and vendor follow-up. Urgency is hard to quantify from the provided sources because severity, CVSS, and exploitation evidence are absent, but broad Snapdragon coverage makes inventory validation important.

Technical view

The CVE describes a potential out-of-bounds read exception when UE receives an unusually large number of padding octets at the beginning of a ROHC header. Affected scope spans many Qualcomm Snapdragon product families and listed chipsets. The bundle provides no CWE, CVSS vector, exploit details, or vendor-specific OEM patch status.

Likely exposure

Exposure is most likely in products using the listed Qualcomm Snapdragon chipsets across mobile, IoT, automotive, compute, connectivity, wearables, and voice/music platforms. Real exposure depends on OEM firmware integration, whether the affected ROHC handling is present, and whether vendor updates have been applied.

Exploitation context

CISA KEV is false in the bundle, and the cited sources do not state active exploitation or public exploit availability. The sources also do not provide enough detail to determine attacker proximity, required network conditions, or practical exploitability.

Researcher notes

The public bundle is sparse: it identifies an out-of-bounds read exception condition in ROHC header handling and a broad Qualcomm affected-product list. It does not provide root-cause code context, exploit preconditions, CVSS, CWE, or a direct standalone patch identifier.

Mitigation direction

  • Check Qualcomm’s March 2021 bulletin and OEM advisories for CVE-2020-11166 guidance.
  • Update affected device firmware through the device OEM or carrier update channel.
  • Prioritize supported Snapdragon-based devices in mobile, IoT, automotive, and embedded fleets.
  • Replace or isolate unsupported devices if no OEM remediation is available.

Validation and detection

  • Inventory devices and map them to Qualcomm chipsets listed in the advisory.
  • Confirm OEM firmware release notes reference CVE-2020-11166 or the March 2021 Qualcomm bulletin.
  • Verify devices are running the latest available OEM or carrier firmware.
  • Review reliability telemetry for unexplained ROHC or header-processing exceptions, if 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-11166 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, AR6003, AR8151, CSR6030, CSRB31024, FSM10055, MDM8207, MDM8215, MDM8215M, MDM8615M, MDM9150, MDM9205, MDM9206, MDM9207, MDM9215, MDM9230, MDM9250, MDM9310, MDM9330, MDM9607, MDM9615, MDM9615M, MDM9625, MDM9628, MDM9630, MDM9635M, 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, PM8018, PM8019, PM8150, PM8150A, PM8150B, PM8150C, PM8150L, PM8250, PM855, PM855A, PM855B, PM855L, PM855P, PM8909, PM8916, PM8937, PM8940, PM8952, PM8953, PM8956, PM8996, PM8998, PMC1000H, PMD9607, PMD9635, PMD9645, PMD9655, PMD9655AU, PME605, PMI632, PMI8937, PMI8940, PMI8952, PMI8994, PMI8996, PMI8998, PMK8001, PMK8002, PMM8 ...[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.