# CVE-2022-22074: Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> An integer overflow in Qualcomm Snapdragon firmware allows memory corruption during WMA file playback, potentially leading to code execution or denial of service.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** 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-gq4x-h8rq-52fw

## What is CVE-2022-22074?

CVE-2022-22074 is a high-severity vulnerability in Qualcomm Apq8009 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

Memory Corruption during wma file playback due to integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 154 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8009w Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9626 Firmware, Qualcomm Mdm9628 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8909w Firmware and 134 more.

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

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

## Is CVE-2022-22074 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22074 is a high-severity vulnerability in Qualcomm Apq8009 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-22074 in the wild and no public exploit code.

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

## Sources

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

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