# CVE-2022-25745: Always Incorrect Control Flow Implementation in MODEM

> Memory corruption in Qualcomm Snapdragon modem firmware allows attackers to execute arbitrary code or escalate privileges via malicious CoAP messages.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3288-5p9j-wphm

## What is CVE-2022-25745?

CVE-2022-25745 is a critical memory corruption vulnerability in Qualcomm Mdm9205 Firmware, published on 4 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Memory corruption in modem due to improper input validation while handling the incoming CoAP message

Weakness: CWE-670 (Always-Incorrect Control Flow Implementation)

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

It affects 5 products.


Products: Qualcomm Mdm9205 Firmware, Qualcomm Qca4004 Firmware, Qualcomm Qts110 Firmware, Qualcomm Snapdragon Wear 1300 Firmware, Qualcomm Wcd9306 Firmware.

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

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

## Is CVE-2022-25745 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9205 Firmware

- [CVE-2019-10612](https://insights.sbomify.com/CVE-2019-10612/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2019-2294](https://insights.sbomify.com/CVE-2019-2294/): 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, Snapdragon Wearables (critical 9.8)
- [CVE-2020-11127](https://insights.sbomify.com/CVE-2020-11127/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-14030](https://insights.sbomify.com/CVE-2019-14030/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)
- [CVE-2019-2267](https://insights.sbomify.com/CVE-2019-2267/): Missing authorization in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25745 is a critical memory corruption vulnerability in Qualcomm Mdm9205 Firmware, published on 4 Apr 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-25745 in the wild and no public exploit code.

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

## Sources

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

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