# CVE-2020-3654: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables > A buffer overflow in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or cause denial of service via crafted SIP packets. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 2 Nov 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-53jx-j2fr-5qgx ## What is CVE-2020-3654? CVE-2020-3654 is a critical memory corruption vulnerability in Qualcomm Apq8053 Firmware, published on 2 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description u'Buffer overflow occurs while processing SIP message packet due to lack of check of index validation before copying into it' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in Agatti, APQ8053, APQ8096AU, APQ8098, Bitra, Kamorta, MSM8905, MSM8909W, MSM8917, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCA6390, QCA6574AU, QCM2150, QCS605, QM215, Rennell, SA6155P, SA8155P, Saipan, SDA660, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130 Weakness: CWE-129 (Improper Validation of Array Index) ## Which versions are affected by CVE-2020-3654? It affects 41 products. Products: Qualcomm Agatti Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Apq8098 Firmware, Qualcomm Bitra Firmware, Qualcomm Kamorta Firmware, Qualcomm Msm8905 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8917 Firmware, Qualcomm Msm8940 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Msm8998 Firmware, Qualcomm Nicobar Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qcm2150 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qm215 Firmware, Qualcomm Rennell Firmware and 21 more. ## How do I fix CVE-2020-3654? No fix has been published for CVE-2020-3654 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-3654 being exploited? There is no known exploitation of CVE-2020-3654 in the wild and no public exploit code. ## Other vulnerabilities in Qualcomm Apq8053 Firmware - [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-11125](https://insights.sbomify.com/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 (high 7.8) - [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-3654 and fix it if it is affected. What it is: CVE-2020-3654 is a critical memory corruption vulnerability in Qualcomm Apq8053 Firmware, published on 2 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-3654 in the wild and no public exploit code. Affected product: Qualcomm Apq8053 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-3654/ (Markdown: https://insights.sbomify.com/CVE-2020-3654/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-3654 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-3654 - OSV: https://osv.dev/vulnerability/CVE-2020-3654 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-3654/ Summaries are generated and may contain mistakes; the official description above is the record.