# CVE-2022-25679: Missing authorization in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> Improper access control in broadcast receivers allows attackers to cause a denial of service in video functionality on Snapdragon devices.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** No
- **Published:** 15 Nov 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-39cv-33wr-fgxh

## What is CVE-2022-25679?

CVE-2022-25679 is a medium-severity missing authorization vulnerability in Qualcomm Aqt1000 Firmware, published on 15 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Denial of service in video due to improper access control in broadcast receivers in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Weakness: CWE-284 (Improper Access Control)

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

It affects 67 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Qcm2290 Firmware, Qualcomm Qcm4290 Firmware, Qualcomm Qcm6490 Firmware, Qualcomm Qcn7606 Firmware, Qualcomm Qcs2290 Firmware, Qualcomm Qcs4290 Firmware, Qualcomm Qcs6490 Firmware, Qualcomm Sd460 Firmware, Qualcomm Sd480 Firmware, Qualcomm Sd662 Firmware, Qualcomm Sd665 Firmware, Qualcomm Sd675 Firmware, Qualcomm Sd678 Firmware, Qualcomm Sd680 Firmware, Qualcomm Sd690 5g Firmware and 47 more.

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

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

## Is CVE-2022-25679 being exploited?

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

## Other vulnerabilities in Qualcomm Aqt1000 Firmware

- [CVE-2025-21479](https://insights.sbomify.com/CVE-2025-21479/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2025-21480](https://insights.sbomify.com/CVE-2025-21480/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2023-28562](https://insights.sbomify.com/CVE-2023-28562/): Buffer Copy Without Checking Size of Input in QESL (critical 9.8)
- [CVE-2022-40514](https://insights.sbomify.com/CVE-2022-40514/): Buffer copy without checking size of input in WLAN Firmware (critical 9.8)
- [CVE-2022-22096](https://insights.sbomify.com/CVE-2022-22096/): Memory corruption in Snapdragon Connectivity, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25679 is a medium-severity missing authorization vulnerability in Qualcomm Aqt1000 Firmware, published on 15 Nov 2022. 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-25679 in the wild and no public exploit code.

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

## Sources

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

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