# CVE-2022-33265: Information exposure in Powerline Communication Firmware

> Memory corruption in Qualcomm Snapdragon Powerline Communication Firmware allows attackers to execute code or disclose information via crafted MMEs.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-vgr9-35rp-jw4x

## What is CVE-2022-33265?

CVE-2022-33265 is a high-severity memory corruption vulnerability in Qualcomm Qca7500 Firmware, published on 6 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Memory corruption due to information exposure in Powerline Communication Firmware while sending different MMEs from a single, unassociated device.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 3 products.


Products: Qualcomm Qca7500 Firmware, Qualcomm Qca7520 Firmware, Qualcomm Qca7550 Firmware.

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

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

## Is CVE-2022-33265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33265 is a high-severity memory corruption vulnerability in Qualcomm Qca7500 Firmware, published on 6 Jan 2023. 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-2022-33265 in the wild and no public exploit code.

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

## Sources

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

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