LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11127: u'Integer overflow can cause a buffer overflow due to lack of table length check in the extensible boot Loa...

u'Integer overflow can cause a buffer overflow due to lack of table length check in the extensible boot Loader during the validation of security metadata while processing objects to be loaded' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in MDM9205, QCM4290, QCS405, QCS410, QCS4290, QCS610, QSM8250, SA415M, SA515M, SA6145P, SA6150P, SA6155, SA6155P, SA8150P, SA8155, SA8155P, SA8195P, SC7180, SC8180X, SC8180X+SDX55, SC8180XP, SDA640, SDA845, SDA855, SDM1000, SDM640, SDM830, SDM845, SDM850, SDX24, SDX50M, SDX55, SDX55M, SM4125, SM4250, SM4250P, SM6115, SM6115P, SM6150, SM6150P, SM6250, SM6250P, SM6350, SM7125, SM7150, SM7150P, SM7225, SM7250, SM7250P, SM8150, SM8150P, SM8250, SXR2130, SXR2130P

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Qualcomm Snapdragon issue affects boot-time processing in many chip families. A malformed object loaded by the extensible boot loader could trigger an integer overflow and buffer overflow while validating security metadata. The business concern is firmware integrity on affected devices, but the provided sources do not give a CVSS score or confirm exploitation.

Executive priority

Treat this as a firmware supply-chain exposure review, not an emergency exploitation response. Prioritize high-value or externally managed device fleets, especially where OEM firmware status is unclear.

Technical view

CVE-2020-11127 is an integer overflow leading to buffer overflow in Qualcomm’s extensible boot loader during validation of security metadata for objects being loaded. The affected list spans Snapdragon Auto, Compute, IoT, Mobile, Voice and Music, and networking products across many chipsets. The source bundle provides no CWE, CVSS vector, exploit detail, or confirmed patch text.

Likely exposure

Exposure is most likely in products embedding the listed Qualcomm chipsets, including mobile, automotive, IoT, compute, modem, and networking devices. Asset owners need device model, chipset, firmware, and OEM support data to determine relevance.

Exploitation context

The provided bundle does not show CISA KEV listing, active exploitation, public exploit availability, or attacker prerequisites. Because the bug is in early boot loader handling, practical exploitation likely depends on device-specific boot chain behavior and update state, which are not detailed here.

Researcher notes

The strongest source detail is the affected chipset list and vulnerability class. Severity is unknown in the bundle, and no exploit or remediation mechanics are provided. Avoid assuming reachability, privileges, or patch availability without OEM-specific advisories.

Mitigation direction

  • Review Qualcomm’s November 2020 security bulletin for vendor guidance.
  • Ask OEMs whether affected device firmware includes the relevant Qualcomm fix.
  • Prioritize supported devices using listed chipsets in sensitive environments.
  • Retire or isolate unsupported devices if no firmware guidance exists.
  • Track firmware update deployment and exception approvals.

Validation and detection

  • Inventory device models and map them to Qualcomm chipsets.
  • Compare chipset names against the affected list in the CVE record.
  • Collect bootloader and firmware versions from OEM management sources.
  • Confirm remediation status against OEM or Qualcomm bulletin references.
  • Document devices where chipset or firmware status cannot be verified.
Prepared
Confidence
medium
Sources
3

Public sources used

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-11127 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and NetworkingMDM9205, QCM4290, QCS405, QCS410, QCS4290, QCS610, QSM8250, SA415M, SA515M, SA6145P, SA6150P, SA6155, SA6155P, SA8150P, SA8155, SA8155P, SA8195P, SC7180, SC8180X, SC8180X+SDX55, SC8180XP, SDA640, SDA845, SDA855, SDM1000, SDM640, SDM830, SDM845, SDM850, SDX24, SDX50M, SDX55, SDX55M, SM4125, SM4250, SM4250P, SM6115, SM6115P, SM6150, SM6150P, SM6250, SM6250P, SM6350, SM7125, SM7150, SM7150P, SM7225, SM7250, SM7250P, SM8150, SM8150P, SM8250, 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.