# CVE-2020-11213: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking > Out-of-bounds reads in Qualcomm Snapdragon firmware allow attackers to read sensitive memory or cause denial of service. - **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:** 21 Jan 2021 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-9c7c-w7q8-pf7c ## What is CVE-2020-11213? CVE-2020-11213 is a critical memory corruption vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking, published on 21 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Out of bound reads might occur in while processing Service descriptor due to improper validation of length of fields in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2020-11213? It affects 555 products. Products: Qualcomm Apq8009, Qualcomm Apq8009w, Qualcomm Apq8016, Qualcomm Apq8017, Qualcomm Apq8037, Qualcomm Apq8039, Qualcomm Apq8052, Qualcomm Apq8053, Qualcomm Apq8056, Qualcomm Apq8064au, Qualcomm Apq8076, Qualcomm Apq8092, Qualcomm Apq8094, Qualcomm Apq8096au, Qualcomm Aqt1000, Qualcomm Ar8031, Qualcomm Ar8035, Qualcomm Ar8151, Qualcomm Ar9380, Qualcomm Csr6030 and 535 more. ## How do I fix CVE-2020-11213? No fix has been published for CVE-2020-11213 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-11213 being exploited? There is no known exploitation of CVE-2020-11213 in the wild and no public exploit code. ## Other vulnerabilities in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking - [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-11213 and fix it if it is affected. What it is: CVE-2020-11213 is a critical memory corruption vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking, published on 21 Jan 2021. 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-11213 in the wild and no public exploit code. Affected product: Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking. 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-11213/ (Markdown: https://insights.sbomify.com/CVE-2020-11213/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11213 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11213 - OSV: https://osv.dev/vulnerability/CVE-2020-11213 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-11213/ Summaries are generated and may contain mistakes; the official description above is the record.