# CVE-2022-33219: Integer Overflow to Buffer Overflow in Automotive

> An integer overflow in Qualcomm Snapdragon automotive firmware allows memory corruption, potentially enabling code execution or privilege escalation.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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:** 6 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-jmcg-v3wf-g69g

## What is CVE-2022-33219?

CVE-2022-33219 is a critical vulnerability in Qualcomm Apq8064au Firmware, published on 6 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption in Automotive due to integer overflow to buffer overflow while registering a new listener with shared buffer.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 24 products.


Products: Qualcomm Apq8064au Firmware, Qualcomm Apq8096au Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qam8295p Firmware, Qualcomm Qca6564a Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6584au Firmware, Qualcomm Qca6595 Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Sa6145p Firmware, Qualcomm Sa6150p Firmware, Qualcomm Sa6155 Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sa8145p Firmware, Qualcomm Sa8150p Firmware, Qualcomm Sa8155 Firmware, Qualcomm Sa8155p Firmware and 4 more.

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

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

## Is CVE-2022-33219 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8064au Firmware

- [CVE-2023-21643](https://insights.sbomify.com/CVE-2023-21643/): Untrusted Pointer Dereference in Automotive (critical 9.1)
- [CVE-2025-27074](https://insights.sbomify.com/CVE-2025-27074/): Incorrect Calculation of Buffer Size in SCE-Mink (high 8.8)
- [CVE-2023-33021](https://insights.sbomify.com/CVE-2023-33021/): Use After Free in Graphics (high 8.4)
- [CVE-2023-21632](https://insights.sbomify.com/CVE-2023-21632/): Stack-based Buffer Overflow in Automotive GPU (high 8.4)
- [CVE-2022-40520](https://insights.sbomify.com/CVE-2022-40520/): Stack based buffer overflow in Core (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33219 is a critical vulnerability in Qualcomm Apq8064au Firmware, published on 6 Jan 2023. 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-33219 in the wild and no public exploit code.

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

## Sources

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

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