# CVE-2022-33221: Buffer over-read in Trusted Execution Environment

> An attacker can read sensitive memory contents in the Trusted Execution Environment via a buffer over-read during metadata verification.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 9 Feb 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r487-8f57-hj96

## What is CVE-2022-33221?

CVE-2022-33221 is a medium-severity vulnerability in Qualcomm Sd 8 Gen1 5g Firmware, published on 9 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Information disclosure in Trusted Execution Environment due to buffer over-read while processing metadata verification requests.

Weakness: CWE-125 (Out-of-bounds Read), CWE-126 (Buffer Over-read)

## Which versions are affected by CVE-2022-33221?

It affects 14 products.


Products: Qualcomm Sd 8 Gen1 5g Firmware, Qualcomm Ssg2115p Firmware, Qualcomm Ssg2125p Firmware, Qualcomm Sxr1230p Firmware, Qualcomm Sxr2230p Firmware, Qualcomm Wcd9380 Firmware, Qualcomm Wcd9385 Firmware, Qualcomm Wcn6855 Firmware, Qualcomm Wcn6856 Firmware, Qualcomm Wcn7850 Firmware, Qualcomm Wcn7851 Firmware, Qualcomm Wsa8830 Firmware, Qualcomm Wsa8832 Firmware, Qualcomm Wsa8835 Firmware.

## How do I fix CVE-2022-33221?

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

## Is CVE-2022-33221 being exploited?

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

## Other vulnerabilities in Qualcomm Sd 8 Gen1 5g Firmware

- [CVE-2022-25723](https://insights.sbomify.com/CVE-2022-25723/): Use after free in Snapdragon Mobile (high 8.4)
- [CVE-2022-22077](https://insights.sbomify.com/CVE-2022-22077/): Use after free in Snapdragon Mobile (high 8.4)
- [CVE-2022-25693](https://insights.sbomify.com/CVE-2022-25693/): Use after free in Snapdragon Connectivity, Snapdragon Mobile (high 8.4)
- [CVE-2021-35091](https://insights.sbomify.com/CVE-2021-35091/): Memory corruption in Snapdragon Connectivity, Snapdragon Mobile (high 8.4)
- [CVE-2021-35110](https://insights.sbomify.com/CVE-2021-35110/): Memory corruption in Snapdragon Connectivity, Snapdragon Mobile (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-33221 and fix it if it is affected.

What it is: CVE-2022-33221 is a medium-severity vulnerability in Qualcomm Sd 8 Gen1 5g Firmware, published on 9 Feb 2023. 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-2022-33221 in the wild and no public exploit code.

Affected product: Qualcomm Sd 8 Gen1 5g 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-2022-33221/ (Markdown: https://insights.sbomify.com/CVE-2022-33221/index.md)
```

## Sources

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

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