LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11125: u'Out of bound access can happen in MHI command process due to lack of check of channel id value received f...

u'Out of bound access can happen in MHI command process due to lack of check of channel id value received from MHI devices' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in Agatti, APQ8009, Bitra, IPQ4019, IPQ5018, IPQ6018, IPQ8064, IPQ8074, Kamorta, MDM9150, MDM9607, MDM9650, MSM8905, MSM8917, MSM8953, Nicobar, QCA6390, QCA9531, QCM2150, QCS404, QCS405, QCS605, QCS610, QM215, QRB5165, Rennell, SA415M, SA515M, SA6155P, SA8155P, Saipan, SC8180X, SDM429, SDM429W, SDM439, SDM450, SDM632, SDM660, SDM670, SDM710, SDM845, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-11125 is a Qualcomm Snapdragon firmware vulnerability involving out-of-bound access in MHI command processing. The public bundle does not provide CVSS, CWE, exact impact, or confirmed exploitation. Business urgency depends on whether your fleet contains the listed Snapdragon platforms and whether OEM firmware guidance identifies available updates.

Executive priority

Handle this as targeted firmware exposure management, not an emergency based on current evidence. Prioritize discovery of affected Qualcomm-based assets and confirm vendor update availability. Escalate if affected chipsets are present in critical, regulated, automotive, or externally exposed environments.

Technical view

The issue is lack of validation of a channel ID value received from MHI devices, allowing out-of-bound access during MHI command processing. Qualcomm lists many Snapdragon Auto, Compute, Connectivity, IoT, Mobile, Voice and Music, Wearables, and networking platforms as affected. Public data in the bundle does not describe exploit prerequisites or impact scope.

Likely exposure

Exposure is most likely in devices using the listed Qualcomm Snapdragon chipsets or platforms. This may include phones, IoT devices, automotive systems, wearables, compute devices, and networking equipment. Confirm through hardware bills of materials, device models, OEM advisories, and firmware security bulletin levels.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. It also lacks proof-of-concept, exploit maturity, attack vector, privileges required, and user interaction details. Do not assume active exploitation or remote exploitability from the provided sources.

Researcher notes

Public evidence is thin: no CVSS vector, CWE, detailed impact, or exploit context is included in the bundle. The affected platform list is broad and hardware-specific, so validation depends on chipset identification and OEM firmware status rather than application scanning alone.

Mitigation direction

  • Inventory assets using the listed Qualcomm Snapdragon platforms or chipsets.
  • Check Qualcomm’s October 2020 bulletin and OEM advisories for fixed firmware guidance.
  • Apply OEM-supported firmware or security updates where available.
  • Prioritize critical, internet-facing, automotive, and unmanaged embedded devices.
  • Track unsupported devices for replacement or compensating controls.

Validation and detection

  • Map device models to Qualcomm chipsets using vendor documentation or asset records.
  • Compare installed firmware against OEM security bulletin or patch-level guidance.
  • Confirm whether any affected platforms appear in production, lab, or field deployments.
  • Review vendor advisories for severity, prerequisites, and remediation status.
  • Monitor CISA KEV and vendor updates for any exploitation status changes.
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-11125 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 Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and NetworkingAgatti, APQ8009, Bitra, IPQ4019, IPQ5018, IPQ6018, IPQ8064, IPQ8074, Kamorta, MDM9150, MDM9607, MDM9650, MSM8905, MSM8917, MSM8953, Nicobar, QCA6390, QCA9531, QCM2150, QCS404, QCS405, QCS605, QCS610, QM215, QRB5165, Rennell, SA415M, SA515M, SA6155P, SA8155P, Saipan, SC8180X, SDM429, SDM429W, SDM439, SDM450, SDM632, SDM660, SDM670, SDM710, SDM845, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130Listed
Weakness

CWE details

No CWE listed

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