CVE-2016-10414

In Android before 2018-04-05 or earlier security patch level on Qualcomm Small Cell SoC, Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear FSM9055, IPQ4019, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 820A, SD 835, SD 845, SD 850, and SDX20, when a hash is passed with zero datalength, the code returns an error, even though zero data length is valid.

Published: 2018-04-18 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-10414 is rated Moderate Risk (64/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.34%). EPSS rose +1.12% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-10414

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.22% 1.34% +1.12%
2 2025-03-30 0.71% 0.22% -0.49%
3 2025-03-29 — 0.71% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-10414

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
10.0 2.0 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 10.0 10.0 [email protected]

Weakness enumeration for CVE-2016-10414

Affected software / configurations for CVE-2016-10414

Vendor Product Version Raw CPE
qualcomm mdm9206_firmware — cpe:2.3:o:qualcomm:mdm9206_firmware:-:*:*:*:*:*:*:*
qualcomm mdm9607_firmware — cpe:2.3:o:qualcomm:mdm9607_firmware:-:*:*:*:*:*:*:*
qualcomm mdm9625_firmware — cpe:2.3:o:qualcomm:mdm9625_firmware:-:*:*:*:*:*:*:*
qualcomm mdm9635m_firmware — cpe:2.3:o:qualcomm:mdm9635m_firmware:-:*:*:*:*:*:*:*
qualcomm mdm9640_firmware — cpe:2.3:o:qualcomm:mdm9640_firmware:-:*:*:*:*:*:*:*
qualcomm mdm9645_firmware — cpe:2.3:o:qualcomm:mdm9645_firmware:-:*:*:*:*:*:*:*
qualcomm mdm9650_firmware — cpe:2.3:o:qualcomm:mdm9650_firmware:-:*:*:*:*:*:*:*
qualcomm mdm9655_firmware — cpe:2.3:o:qualcomm:mdm9655_firmware:-:*:*:*:*:*:*:*
qualcomm msm8909w_firmware — cpe:2.3:o:qualcomm:msm8909w_firmware:-:*:*:*:*:*:*:*
qualcomm sd_210_firmware — cpe:2.3:o:qualcomm:sd_210_firmware:-:*:*:*:*:*:*:*
qualcomm sd_212_firmware — cpe:2.3:o:qualcomm:sd_212_firmware:-:*:*:*:*:*:*:*
qualcomm sd_205_firmware — cpe:2.3:o:qualcomm:sd_205_firmware:-:*:*:*:*:*:*:*
qualcomm sd_400_firmware — cpe:2.3:o:qualcomm:sd_400_firmware:-:*:*:*:*:*:*:*
qualcomm sd_410_firmware — cpe:2.3:o:qualcomm:sd_410_firmware:-:*:*:*:*:*:*:*
qualcomm sd_412_firmware — cpe:2.3:o:qualcomm:sd_412_firmware:-:*:*:*:*:*:*:*
qualcomm sd_425_firmware — cpe:2.3:o:qualcomm:sd_425_firmware:-:*:*:*:*:*:*:*
qualcomm sd_430_firmware — cpe:2.3:o:qualcomm:sd_430_firmware:-:*:*:*:*:*:*:*
qualcomm sd_450_firmware — cpe:2.3:o:qualcomm:sd_450_firmware:-:*:*:*:*:*:*:*
qualcomm sd_615_firmware — cpe:2.3:o:qualcomm:sd_615_firmware:-:*:*:*:*:*:*:*
qualcomm sd_616_firmware — cpe:2.3:o:qualcomm:sd_616_firmware:-:*:*:*:*:*:*:*
qualcomm sd_415_firmware — cpe:2.3:o:qualcomm:sd_415_firmware:-:*:*:*:*:*:*:*
qualcomm sd_617_firmware — cpe:2.3:o:qualcomm:sd_617_firmware:-:*:*:*:*:*:*:*
qualcomm sd_625_firmware — cpe:2.3:o:qualcomm:sd_625_firmware:-:*:*:*:*:*:*:*
qualcomm sd_650_firmware — cpe:2.3:o:qualcomm:sd_650_firmware:-:*:*:*:*:*:*:*
qualcomm sd_652_firmware — cpe:2.3:o:qualcomm:sd_652_firmware:-:*:*:*:*:*:*:*
qualcomm sd_800_firmware — cpe:2.3:o:qualcomm:sd_800_firmware:-:*:*:*:*:*:*:*
qualcomm sd_808_firmware — cpe:2.3:o:qualcomm:sd_808_firmware:-:*:*:*:*:*:*:*
qualcomm sd_810_firmware — cpe:2.3:o:qualcomm:sd_810_firmware:-:*:*:*:*:*:*:*
qualcomm sd_820_firmware — cpe:2.3:o:qualcomm:sd_820_firmware:-:*:*:*:*:*:*:*
qualcomm sd_835_firmware — cpe:2.3:o:qualcomm:sd_835_firmware:-:*:*:*:*:*:*:*
qualcomm sd_845_firmware — cpe:2.3:o:qualcomm:sd_845_firmware:-:*:*:*:*:*:*:*
qualcomm sdx20_firmware — cpe:2.3:o:qualcomm:sdx20_firmware:-:*:*:*:*:*:*:*
qualcomm sd_850_firmware — cpe:2.3:o:qualcomm:sd_850_firmware:-:*:*:*:*:*:*:*
qualcomm sd_820a_firmware — cpe:2.3:o:qualcomm:sd_820a_firmware:-:*:*:*:*:*:*:*

References for CVE-2016-10414

cvelogic Threat Intelligence