# CVE-2020-11122: Null dereference in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile

> A null pointer dereference in Qualcomm Snapdragon firmware allows attackers to cause a denial of service by playing a crafted MKV file.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gqwc-24f2-x3gv

## What is CVE-2020-11122?

CVE-2020-11122 is a medium-severity vulnerability in Qualcomm Apq8098 Firmware, published on 8 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

u'Null Pointer exception while playing crafted mkv file as data stream get deleted on secondary invalid configuration' in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile in APQ8098, Bitra, Kamorta, SA6155P, Saipan, SM6150, SM7150, SM8150, SM8250, SXR2130

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2020-11122?

It affects 10 products.


Products: Qualcomm Apq8098 Firmware, Qualcomm Bitra Firmware, Qualcomm Kamorta Firmware, Qualcomm Sa6155p Firmware, Qualcomm Saipan Firmware, Qualcomm Sm6150 Firmware, Qualcomm Sm7150 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8250 Firmware, Qualcomm Sxr2130 Firmware.

## How do I fix CVE-2020-11122?

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

## Is CVE-2020-11122 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8098 Firmware

- [CVE-2020-3667](https://insights.sbomify.com/CVE-2020-3667/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-3669](https://insights.sbomify.com/CVE-2020-3669/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2019-14112](https://insights.sbomify.com/CVE-2019-14112/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2019-14086](https://insights.sbomify.com/CVE-2019-14086/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11206](https://insights.sbomify.com/CVE-2020-11206/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11122 and fix it if it is affected.

What it is: CVE-2020-11122 is a medium-severity vulnerability in Qualcomm Apq8098 Firmware, published on 8 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-11122 in the wild and no public exploit code.

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

## Sources

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

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