# CVE-2022-33216: Improper Input Validation in Automotive

> Attackers can cause a transient denial of service in Qualcomm Snapdragon automotive systems by providing malformed ELF files.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-89gg-r749-m2mc

## What is CVE-2022-33216?

CVE-2022-33216 is a medium-severity denial of service vulnerability in Qualcomm Qam8295p Firmware, published on 9 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Transient Denial-of-service in Automotive due to improper input validation while parsing ELF file.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 18 products.


Products: Qualcomm Qam8295p Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au 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, Qualcomm Sa8195p Firmware, Qualcomm Sa8295p Firmware, Qualcomm Sa8540p Firmware, Qualcomm Sa9000p Firmware.

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

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

## Is CVE-2022-33216 being exploited?

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

## Other vulnerabilities in Qualcomm Qam8295p Firmware

- [CVE-2023-33039](https://insights.sbomify.com/CVE-2023-33039/): Use After Free in Automotive Display (high 8.4)
- [CVE-2023-21642](https://insights.sbomify.com/CVE-2023-21642/): Improper Access Control in HAB Memory Management (high 8.4)
- [CVE-2022-40539](https://insights.sbomify.com/CVE-2022-40539/): Improper Validation of Array Index in Automotive Android OS (high 8.4)
- [CVE-2022-33274](https://insights.sbomify.com/CVE-2022-33274/): Improper validation of array index in Android Core (high 8.4)
- [CVE-2022-33300](https://insights.sbomify.com/CVE-2022-33300/): Improper input validation in Automotive Android OS (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33216 is a medium-severity denial of service vulnerability in Qualcomm Qam8295p Firmware, published on 9 Feb 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-33216 in the wild and no public exploit code.

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

## Sources

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

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