# CVE-2020-3622: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking > Attackers can exploit missing NULL termination in shared memory channel names to cause memory corruption, potentially leading to code execution on 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:** No - **Published:** 8 Sep 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-wxhm-qq5v-rf47 ## What is CVE-2020-3622? CVE-2020-3622 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 8 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description u'Channel name string which has been read from shared memory is potentially subjected to string manipulations but not validated for NULL termination can results into memory corruption' in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, Bitra, IPQ6018, IPQ8074, Kamorta, MDM9150, MDM9205, MDM9206, MDM9607, MDM9640, MDM9645, MDM9650, MDM9655, MSM8905, MSM8909, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996, MSM8996AU, MSM8998, Nicobar, QCA8081, QCM2150, QCN7605, QCS404, QCS405, QCS605, QCS610, QM215, Rennell, SA415M, SA6155P, Saipan, SC7180, SC8180X, SDA660, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, SDX20, SDX24, SDX55, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130 Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2020-3622? It affects 130 products. Products: Qualcomm Apq8009, Qualcomm Apq8009 Firmware, Qualcomm Apq8017, Qualcomm Apq8017 Firmware, Qualcomm Apq8053, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au, Qualcomm Apq8096au Firmware, Qualcomm Apq8098, Qualcomm Apq8098 Firmware, Qualcomm Bitra, Qualcomm Bitra Firmware, Qualcomm Ipq6018, Qualcomm Ipq6018 Firmware, Qualcomm Ipq8074, Qualcomm Ipq8074 Firmware, Qualcomm Kamorta, Qualcomm Kamorta Firmware, Qualcomm Mdm9150, Qualcomm Mdm9150 Firmware and 110 more. ## How do I fix CVE-2020-3622? No fix has been published for CVE-2020-3622 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-3622 being exploited? There is no known exploitation of CVE-2020-3622 in the wild and no public exploit code. ## Other vulnerabilities in Qualcomm Apq8009 Firmware - [CVE-2020-11283](https://insights.sbomify.com/CVE-2020-11283/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8) - [CVE-2020-11136](https://insights.sbomify.com/CVE-2020-11136/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8) - [CVE-2020-11137](https://insights.sbomify.com/CVE-2020-11137/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8) - [CVE-2020-11138](https://insights.sbomify.com/CVE-2020-11138/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8) - [CVE-2020-11143](https://insights.sbomify.com/CVE-2020-11143/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-3622 and fix it if it is affected. What it is: CVE-2020-3622 is a high-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 8 Sep 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-3622 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-3622/ (Markdown: https://insights.sbomify.com/CVE-2020-3622/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-3622 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-3622 - OSV: https://osv.dev/vulnerability/CVE-2020-3622 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-3622/ Summaries are generated and may contain mistakes; the official description above is the record.