# CVE-2020-11170: 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

> Out-of-bounds memory access in Snapdragon chipsets allows attackers to execute code or cause denial of service via crafted Vorbis audio files.

- **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:** 22 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5hmm-wjg3-4m2m

## What is CVE-2020-11170?

CVE-2020-11170 is a critical memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 22 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Out of bound memory access while playing music playbacks with crafted vorbis content due to improper checks in header extraction 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

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2020-11170?

It affects 505 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8009w Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8030 Firmware, Qualcomm Apq8037 Firmware, Qualcomm Apq8052 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8056 Firmware, Qualcomm Apq8060a Firmware, Qualcomm Apq8062 Firmware, Qualcomm Apq8064 Firmware, Qualcomm Apq8064au Firmware, Qualcomm Apq8076 Firmware, Qualcomm Apq8084 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar6003 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Ar8151 Firmware and 485 more.

## How do I fix CVE-2020-11170?

No fix has been published for CVE-2020-11170 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-11170 being exploited?

There is no known exploitation of CVE-2020-11170 in the wild and no public exploit code.

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11170 and fix it if it is affected.

What it is: CVE-2020-11170 is a critical memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 22 Feb 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-11170 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-11170/ (Markdown: https://insights.sbomify.com/CVE-2020-11170/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11170
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11170
- OSV: https://osv.dev/vulnerability/CVE-2020-11170

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-11170/
Summaries are generated and may contain mistakes; the official description above is the record.