# CVE-2016-10411: Denial of service in Snapdragon Mobile

> A malformed RTCP packet causes the RTP daemon to crash, terminating Voice over LTE calls on affected Qualcomm Snapdragon devices.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 18 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-qh5m-f9qx-pv32

## What is CVE-2016-10411?

CVE-2016-10411 is a high-severity denial of service vulnerability in Qualcomm Sd 205 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 SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, and SD 835, RTP daemon crashes and terminates VT call when UE receives RTCP unknown APP packet report which caused the parser to miss an end of RTCP packet length and go on forever looking for it, even going beyond the limits of the RTCP Packet length.

Weakness: CWE-399

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

It affects 20 products.


Products: Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 400 Firmware, Qualcomm Sd 410 Firmware, Qualcomm Sd 412 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 430 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 617 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 800 Firmware, Qualcomm Sd 808 Firmware, Qualcomm Sd 810 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 835 Firmware.

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

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

## Is CVE-2016-10411 being exploited?

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

## Other vulnerabilities in Qualcomm Sd 205 Firmware

- [CVE-2014-10056](https://insights.sbomify.com/CVE-2014-10056/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2015-9205](https://insights.sbomify.com/CVE-2015-9205/): Memory corruption in Snapdragon Mobile, Snapdragon Wear (critical 9.8)
- [CVE-2016-10407](https://insights.sbomify.com/CVE-2016-10407/): Integer overflow in Snapdragon Mobile (critical 9.8)
- [CVE-2016-10458](https://insights.sbomify.com/CVE-2016-10458/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2016-10467](https://insights.sbomify.com/CVE-2016-10467/): Weak cryptography in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-10411 is a high-severity denial of service vulnerability in Qualcomm Sd 205 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-10411 in the wild and no public exploit code.

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

## Sources

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

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