dbcve.org
Mdm9205 FirmwareOperating system · Qualcomm

CVE-2020-11127

HIGH · 7.8 CVSS v3.1 Published 2020-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Integer overflow in Qualcomm's extensible boot Loader (XBL) allows buffer overflow due to missing table length check during security metadata validation when processing objects to be loaded. This affects the boot chain security of multiple Snapdragon chipset generations.

MitigationDeploy vendor firmware updates from Qualcomm to affected devices; coordinate with OEM/device manufacturers for patch integration and OTA deployment. No workarounds available for this low-level boot loader vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mdm9205 FirmwareOperating system
Affected:all versions
Qcm4290 FirmwareOperating system
Affected:all versions
Qcs405 FirmwareOperating system
Affected:all versions
Qcs410 FirmwareOperating system
Affected:all versions
Qcs4290 FirmwareOperating system
Affected:all versions
Qcs610 FirmwareOperating system
Affected:all versions
Qsm8250 FirmwareOperating system
Affected:all versions
Sa415m FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device chipset model
    Retrieve the chipset or SoC model from system information files such as /proc/cpuinfo, /proc/device-tree/compatible, or through vendor-specific commands like 'cat /sys/devices/system/soc/soc0/part_number' or 'dmesg | grep -i chip'
    Affected if The chipset matches one of the following: Mdm9205, Qcm4290, Qcs405, Qcs410, Qcs4290, Qcs610, Qsm8250, or Sa415m
  2. Confirm XBL bootloader presence
    Check boot partition or bootloader configuration files for XBL image presence. On Android devices, examine /dev/block/*/boot or use 'ls -la /boot' if accessible. Review boot logs via 'dmesg' or 'logcat' for XBL-related entries during early boot.
    Affected if The XBL bootloader is present and loads during the device boot sequence
  3. Verify firmware version
    Query the current firmware version through device information settings, manufacturer tools, or by extracting version strings from the bootloader image itself using tools like 'strings' or binwalk on a dumped firmware image.
    Affected if Any firmware version is installed on an affected chipset since all versions are vulnerable

A device is affected if it contains any of the listed Qualcomm chipsets (Mdm9205, Qcm4290, Qcs405, Qcs410, Qcs4290, Qcs610, Qsm8250, Sa415m) and runs the XBL bootloader, as the vulnerability exists in all firmware versions of these products.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Deploy vendor firmware updates from Qualcomm to affected devices; coordinate with OEM/device manufacturers for patch integration and OTA deployment. No workarounds available for this low-level boot loader vulnerability.

Fix this in Mdm9205 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation4.0 h
  • Testing20.0 h
  • Review / QA12.0 h
48.0 hours of engineering $8,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-11127 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data