# CVE-2019-10622: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

> Out-of-bounds memory access in ADSP message parsing allows attackers to execute arbitrary code or cause denial of service on Qualcomm Snapdragon devices.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 16 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-23rx-f2xv-5pg9

## What is CVE-2019-10622?

CVE-2019-10622 is a critical memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 16 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Out of bound memory access can happen while parsing ADSP message due to lack of check of size of payload received from userspace in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8096AU, IPQ4019, IPQ6018, IPQ8064, IPQ8074, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, QCN7605, QCS605, SC8180X, SDM710, SDX24, SDX55, SM8150, SM8250, SXR2130

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

## Which versions are affected by CVE-2019-10622?

It affects 20 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8074 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207c Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Qcn7605 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sc8180x Firmware, Qualcomm Sdm710 Firmware, Qualcomm Sdx24 Firmware, Qualcomm Sdx55 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr2130 Firmware.

## How do I fix CVE-2019-10622?

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

## Is CVE-2019-10622 being exploited?

There is no known exploitation of CVE-2019-10622 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-2019-10622 and fix it if it is affected.

What it is: CVE-2019-10622 is a critical memory corruption vulnerability in Qualcomm Apq8009 Firmware, published on 16 Apr 2020. 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-2019-10622 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-2019-10622/ (Markdown: https://insights.sbomify.com/CVE-2019-10622/index.md)
```

## Sources

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

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