# CVE-2020-11308: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

> A buffer overflow in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via crafted ASCII strings.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** 2783331, A-175038288, ASB-A-175038288, GHSA-59gm-4h96-737v

## What is CVE-2020-11308?

CVE-2020-11308 is a medium-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 17 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow occurs when trying to convert ASCII string to Unicode string if the actual size is more than required in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

Weakness: CWE-129 (Improper Validation of Array Index)

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

It affects 333 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Ar8151 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Fsm10055 Firmware, Qualcomm Fsm10056 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9655 Firmware, Qualcomm Pm3003a Firmware, Qualcomm Pm4125 Firmware, Qualcomm Pm4250 Firmware, Qualcomm Pm456 Firmware, Qualcomm Pm6125 Firmware, Qualcomm Pm6150 Firmware, Qualcomm Pm6150a Firmware, Qualcomm Pm6150l Firmware and 313 more.

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

Apply the vendor's patch.

## Is CVE-2020-11308 being exploited?

There is no known exploitation of CVE-2020-11308 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-11308 and fix it if it is affected.

What it is: CVE-2020-11308 is a medium-severity memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 17 Mar 2021. 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-11308 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-11308/ (Markdown: https://insights.sbomify.com/CVE-2020-11308/index.md)
```

## Sources

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

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