dbcve.org
Sd 210 FirmwareOperating system · Qualcomm

CVE-2016-10411

HIGH · 7.5 CVSS v3.0 Published 2018-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The RTP daemon on affected Qualcomm Snapdragon devices lacks proper bounds checking when parsing RTCP unknown APP packets. When receiving a malformed RTCP packet with an unknown APP type, the parser fails to recognize the packet length field, causing an infinite loop that reads beyond packet boundaries, exhausting resources and crashing the daemon.

MitigationApply the appropriate Qualcomm firmware/hardware security patch dated 2018-04-05 or later, which corrects the RTCP packet parsing logic to properly validate packet length boundaries before processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 400 FirmwareOperating system
Affected:all versions
Sd 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 430 FirmwareOperating system
Affected:all versions
Sd 450 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the system processor
    Check the system's hardware specifications or /proc/cpuinfo to determine if the device uses a Qualcomm Snapdragon Sd 210, Sd 212, Sd 205, Sd 400, Sd 410, Sd 412, Sd 430, or Sd 450 chipset
    Affected if The processor is one of the listed Snapdragon variants and is therefore potentially affected
  2. Check the firmware version
    Retrieve the firmware version from the device (typically via system settings, /proc/version, or manufacturer documentation) and compare it against the 2018-04-05 patch date
    Affected if The firmware version is from before 2018-04-05 or cannot be confirmed as patched, indicating the RTCP parsing vulnerability may still be present
  3. Verify the RTP daemon is active
    Check running processes for the RTP daemon or RTCP service (commands like 'ps' or 'service list' depending on the device OS)
    Affected if The RTP daemon is running and reachable over the network, making it exploitable via malformed RTCP packets
  4. Inspect for crash logs or resource exhaustion
    Review system logs (/var/log, dmesg, or Android logs) for RTP daemon crashes, restarts, or resource exhaustion events around the time of potential network activity
    Affected if The RTP daemon has crashed or exhibited abnormal resource consumption with RTCP-related error messages, indicating possible exploitation of this flaw

A defender is affected if the device runs on a listed Qualcomm Snapdragon chipset with pre-2018-04-05 firmware and has the RTP daemon active and network-reachable, allowing malformed RTCP unknown APP packets to trigger the infinite loop condition.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate Qualcomm firmware/hardware security patch dated 2018-04-05 or later, which corrects the RTCP packet parsing logic to properly validate packet length boundaries before processing.

Fix this in Sd 210 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10411 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10411 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data