# CVE-2020-11125: Memory corruption 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 > Out-of-bounds access in MHI command processing allows attackers to execute arbitrary code or escalate privileges on affected Qualcomm Snapdragon devices. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Nov 2020 - **Updated:** 4 Aug 2024 - **Also known as:** 2617422, 2673763, A-160605820, ASB-A-160605820, GHSA-9qwj-267h-cmr3 ## What is CVE-2020-11125? CVE-2020-11125 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 2 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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 Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2020-11125? It affects 48 products. Products: Qualcomm Agatti Firmware, Qualcomm Apq8009 Firmware, Qualcomm Bitra Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Ipq5018 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8074 Firmware, Qualcomm Kamorta Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8905 Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Nicobar Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca9531 Firmware, Qualcomm Qcm2150 Firmware, Qualcomm Qcs404 Firmware and 28 more. ## How do I fix CVE-2020-11125? Apply the vendor's patch. ## Is CVE-2020-11125 being exploited? There is no known exploitation of CVE-2020-11125 in the wild and no public exploit code. ## Other vulnerabilities in Qualcomm Apq8009 Firmware - [CVE-2020-3654](https://insights.sbomify.com/CVE-2020-3654/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8) - [CVE-2020-3673](https://insights.sbomify.com/CVE-2020-3673/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8) - [CVE-2020-3692](https://insights.sbomify.com/CVE-2020-3692/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8) - [CVE-2020-3670](https://insights.sbomify.com/CVE-2020-3670/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.1) - [CVE-2020-11162](https://insights.sbomify.com/CVE-2020-11162/): Memory corruption 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 (high 7.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-11125 and fix it if it is affected. What it is: CVE-2020-11125 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 2 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-11125 in the wild and no public exploit code. Affected product: Qualcomm Apq8009 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-11125/ (Markdown: https://insights.sbomify.com/CVE-2020-11125/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11125 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11125 - OSV: https://osv.dev/vulnerability/CVE-2020-11125 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-11125/ Summaries are generated and may contain mistakes; the official description above is the record.