# CVE-2022-25653: Information disclosure in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> An attacker can disclose sensitive information via a buffer over-read when processing a malicious AVI file on Qualcomm Snapdragon devices.

- **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:** 16 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wrgm-m92f-pf2v

## What is CVE-2022-25653?

CVE-2022-25653 is a medium-severity vulnerability in Qualcomm Apq8053 Firmware, published on 16 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Information disclosure in video due to buffer over-read while processing avi file in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 90 products.


Products: Qualcomm Apq8053 Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Msm8953 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qcm4290 Firmware, Qualcomm Qcm6490 Firmware, Qualcomm Qcs410 Firmware, Qualcomm Qcs4290 Firmware, Qualcomm Qcs603 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qcs610 Firmware, Qualcomm Qcs6490 Firmware, Qualcomm Qualcomm215 Firmware, Qualcomm Sd429 Firmware, Qualcomm Sd460 Firmware and 70 more.

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

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

## Is CVE-2022-25653 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8053 Firmware

- [CVE-2022-22071](https://insights.sbomify.com/CVE-2022-22071/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11153](https://insights.sbomify.com/CVE-2020-11153/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-3703](https://insights.sbomify.com/CVE-2020-3703/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2019-14080](https://insights.sbomify.com/CVE-2019-14080/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (critical 9.8)
- [CVE-2020-3628](https://insights.sbomify.com/CVE-2020-3628/): Information disclosure in Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25653 is a medium-severity vulnerability in Qualcomm Apq8053 Firmware, published on 16 Sep 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-25653 in the wild and no public exploit code.

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

## Sources

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

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