dbcve.org
Msm8998 FirmwareOperating system · Qualcomm

CVE-2020-11133

HIGH · 7.8 CVSS v3.1 Published 2020-09-08
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'Possible out of bound array write in rxdco cal utility due to lack of array bound check' in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in MSM8998, QCS605, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SXR1130

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 · moderate confidence

An out-of-bounds array write vulnerability exists in the rxdco calibration utility due to missing array bounds checking, allowing a local attacker to write beyond array boundaries and potentially execute arbitrary code or cause denial of service.

MitigationApply Qualcomm vendor firmware updates for affected chipsets (MSM8998, QCS605, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SXR1130) through device manufacturer or carrier deployment channels.

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
Msm8998 FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Sda845 FirmwareOperating system
Affected:all versions
Sdm630 FirmwareOperating system
Affected:all versions
Sdm636 FirmwareOperating system
Affected:all versions
Sdm660 FirmwareOperating system
Affected:all versions
Sdm670 FirmwareOperating system
Affected:all versions
Sdm710 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
    On Android devices, run 'getprop ro.hardware' or check /proc/cpuinfo for the processor identifier. On other embedded systems, consult system documentation or boot logs for the Qualcomm chipset name.
    Affected if The chipset matches one of the affected models: MSM8998, QCS605, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, or SDM845.
  2. Determine the firmware version
    Check the firmware or baseband version via 'getprop ro.build.description', 'getprop gsm.version.baseband', or system firmware version fields. Consult device manufacturer documentation for firmware version retrieval methods specific to your device.
    Affected if The firmware version is earlier than the vendor patch date for this CVE, or if the chipset is on the affected list and no patch has been applied.
  3. Locate the rxdco calibration utility
    Search for the rxdco binary or calibration utility on the device using 'find / -name *rxdco* 2>/dev/null' or check common firmware utility locations. This utility is typically found in firmware or calibration data directories.
    Affected if The rxdco utility is present on the device, indicating the vulnerable component exists.
  4. Verify firmware update status
    Contact the device manufacturer or carrier to confirm whether a firmware update addressing CVE-2020-11133 has been applied. Check vendor security bulletins for patch availability for your specific device model.
    Affected if No vendor firmware patch for CVE-2020-11133 has been applied to the device.

A defender is affected if their device uses one of the listed Qualcomm chipsets (MSM8998, QCS605, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710) and the rxdco calibration utility is present without the vendor-specific firmware patch for this vulnerability.

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

Apply Qualcomm vendor firmware updates for affected chipsets (MSM8998, QCS605, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SXR1130) through device manufacturer or carrier deployment channels.

Fix this in Msm8998 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11133 — 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-11133 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