# CVE-2016-10496: Null dereference in Snapdragon Mobile

> A null pointer dereference during SSL handshake in Qualcomm Snapdragon Mobile chipsets can cause a denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h3j5-6crw-xhfj

## What is CVE-2016-10496?

CVE-2016-10496 is a critical vulnerability in Qualcomm Mdm9635m Firmware, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MDM9635M, SD 210/SD 212/SD 205, SD 410/12, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, and SD 810, A NULL pointer dereference can occur during an SSL handshake.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2016-10496?

It affects 15 products.


Products: Qualcomm Mdm9635m Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 412 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 808 Firmware, Qualcomm Sd 810 Firmware.

## How do I fix CVE-2016-10496?

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

## Is CVE-2016-10496 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9635m Firmware

- [CVE-2017-18160](https://insights.sbomify.com/CVE-2017-18160/): Hardcoded credentials in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2014-9985](https://insights.sbomify.com/CVE-2014-9985/): Race condition in Snapdragon Mobile (critical 9.8)
- [CVE-2016-10494](https://insights.sbomify.com/CVE-2016-10494/): Integer overflow in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2016-10495](https://insights.sbomify.com/CVE-2016-10495/): Integer overflow in Snapdragon Mobile (critical 9.8)
- [CVE-2016-10433](https://insights.sbomify.com/CVE-2016-10433/): Race condition in Snapdragon Automobile, Snapdragon Mobile, Snapdragon Wear (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10496 and fix it if it is affected.

What it is: CVE-2016-10496 is a critical vulnerability in Qualcomm Mdm9635m Firmware, published on 18 Apr 2018. 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-2016-10496 in the wild and no public exploit code.

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

## Sources

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

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