# CVE-2020-11294: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> An out-of-bounds write in the logger allows attackers to execute arbitrary code or escalate privileges on Qualcomm Snapdragon devices.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cxw5-q7v9-8pf8

## What is CVE-2020-11294?

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

### Official description

Out of bound write in logger due to prefix size is not validated while prepended to logging string in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

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

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

It affects 244 products.


Products: Qualcomm Ar8035 Firmware, Qualcomm Pm215 Firmware, Qualcomm Pm3003a Firmware, Qualcomm Pm6125 Firmware, Qualcomm Pm6150 Firmware, Qualcomm Pm6150a Firmware, Qualcomm Pm6150l Firmware, Qualcomm Pm6350 Firmware, Qualcomm Pm640a Firmware, Qualcomm Pm640l Firmware, Qualcomm Pm640p Firmware, Qualcomm Pm670 Firmware, Qualcomm Pm670l Firmware, Qualcomm Pm7150a Firmware, Qualcomm Pm7150l Firmware, Qualcomm Pm7250 Firmware, Qualcomm Pm7250b Firmware, Qualcomm Pm8005 Firmware, Qualcomm Pm8008 Firmware, Qualcomm Pm8009 Firmware and 224 more.

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

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

## Is CVE-2020-11294 being exploited?

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

## Other vulnerabilities in Qualcomm Ar8035 Firmware

- [CVE-2023-33106](https://insights.sbomify.com/CVE-2023-33106/): Qualcomm Multiple Chipsets Use of Out-of-Range Pointer Offset (high 8.4, exploited in the wild)
- [CVE-2024-45569](https://insights.sbomify.com/CVE-2024-45569/): Improper Validation of Array Index in WLAN Host Communication (critical 9.8)
- [CVE-2024-21473](https://insights.sbomify.com/CVE-2024-21473/): Improper Input Validation in WIN SON (critical 9.8)
- [CVE-2023-28582](https://insights.sbomify.com/CVE-2023-28582/): Buffer Copy Without Checking Size of Input in Data Modem (critical 9.8)
- [CVE-2023-43552](https://insights.sbomify.com/CVE-2023-43552/): Use After Free in WLAN Host Communication (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11294 is a medium-severity memory corruption vulnerability in Qualcomm Ar8035 Firmware, published on 7 May 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-11294 in the wild and no public exploit code.

Affected product: Qualcomm Ar8035 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-11294/ (Markdown: https://insights.sbomify.com/CVE-2020-11294/index.md)
```

## Sources

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

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