# CVE-2020-11221: Information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking

> A non-secure entity can extract secure QTEE diagnostic information in clear text due to insufficient syscall handler checks in Qualcomm Snapdragon chipsets.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 17 Mar 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pxrx-xq88-m2w4

## What is CVE-2020-11221?

CVE-2020-11221 is a medium-severity 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

Usage of syscall by non-secure entity can allow extraction of secure QTEE diagnostic information in clear text form due to insufficient checks in the syscall handler and leads to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 401 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8009w Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8037 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8084 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Ar8151 Firmware, Qualcomm Csr6030 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Mdm8207 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9205 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207 Firmware, Qualcomm Mdm9230 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9330 Firmware and 381 more.

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

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

## Is CVE-2020-11221 being exploited?

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

What it is: CVE-2020-11221 is a medium-severity 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-11221 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-11221/ (Markdown: https://insights.sbomify.com/CVE-2020-11221/index.md)
```

## Sources

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

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