# CVE-2022-25728: Buffer Over-read in MODEM

> An attacker can read sensitive memory contents via a buffer over-read in the modem firmware when processing DNS responses.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3j56-76c6-9xf6

## What is CVE-2022-25728?

CVE-2022-25728 is a high-severity vulnerability in Qualcomm Ar8031 Firmware, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Information disclosure in modem due to buffer over-read while processing response from DNS server

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

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

It affects 34 products.


Products: Qualcomm Ar8031 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Mdm8207 Firmware, Qualcomm Mdm9205 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Qca4004 Firmware, Qualcomm Qca4020 Firmware, Qualcomm Qca4024 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qts110 Firmware, Qualcomm Ssg2115p Firmware, Qualcomm Ssg2125p Firmware, Qualcomm Sxr1230p Firmware, Qualcomm Sxr2230p Firmware, Qualcomm Wcd9306 Firmware, Qualcomm Wcd9330 Firmware, Qualcomm Wcd9335 Firmware and 14 more.

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

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

## Is CVE-2022-25728 being exploited?

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

## Other vulnerabilities in Qualcomm Ar8031 Firmware

- [CVE-2025-27038](https://insights.sbomify.com/CVE-2025-27038/): Qualcomm Multiple Chipsets Use-After-Free (high 7.5, exploited in the wild)
- [CVE-2022-25729](https://insights.sbomify.com/CVE-2022-25729/): Improper Input Validation in MODEM (critical 9.8)
- [CVE-2022-25727](https://insights.sbomify.com/CVE-2022-25727/): Memory corruption in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music (critical 9.8)
- [CVE-2021-30285](https://insights.sbomify.com/CVE-2021-30285/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.3)
- [CVE-2021-30275](https://insights.sbomify.com/CVE-2021-30275/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25728 is a high-severity vulnerability in Qualcomm Ar8031 Firmware, published on 9 Feb 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-25728 in the wild and no public exploit code.

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

## Sources

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

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