sd_652_firmware is a software product offered by qualcomm. This product is widely deployed in production environments, making vulnerability monitoring essential for organizations relying on it. Security vulnerabilities in products of this category can affect system availability, data confidentiality, and integrity across entire networks. The significant number of reported vulnerabilities indicates this product has received substantial security scrutiny and community focus over time. Regular assessment of known vulnerabilities and timely patching are fundamental components of responsible system administration for any deployment of this software.
SecUtils has identified 315 known vulnerabilities affecting qualcomm sd_652_firmware. This includes 168 critical-severity issues and 114 high-severity issues that warrant immediate attention. Vulnerabilities in this product have been disclosed spanning from 2018 to 2024, indicating a sustained research interest and ongoing security attention. 33 medium-severity issues complete the vulnerability landscape. Organizations should prioritize patching based on deployment context, asset criticality, and exploitation likelihood rather than severity alone.
| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2017-14910 | 2018-02-23 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-17773 | 2018-03-15 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-14911 | 2018-03-30 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-14912 | 2018-03-30 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-14913 | 2018-03-30 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-14915 | 2018-03-30 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18071 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18072 | 2018-04-11 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-18126 | 2018-04-11 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-18127 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18130 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18135 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18136 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18137 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18138 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18139 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18140 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18144 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18145 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-18146 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-8274 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-8275 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-3590 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-3591 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-3592 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-3593 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-3594 | 2018-04-11 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-10048 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-10052 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-10053 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-10054 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-10058 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2014-10062 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2014-9986 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2014-9987 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-9988 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-9989 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-9990 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-9991 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-9993 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2014-9997 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9108 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9109 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9110 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9111 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9113 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9114 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9115 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9116 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9119 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9120 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9122 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9123 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9126 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9128 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9129 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9130 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9133 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9135 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9136 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9137 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9138 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9139 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9140 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9142 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9144 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9145 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9148 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9149 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9153 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9157 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9158 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9159 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9160 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9161 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9162 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9163 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9164 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9165 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9166 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9167 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9169 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9170 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9171 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9172 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9173 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9174 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9175 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9176 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9177 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9178 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9180 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9181 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9182 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9183 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9184 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9185 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9186 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9187 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9188 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9191 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9192 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9193 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9194 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9195 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9197 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9198 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9200 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9201 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9202 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9203 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9206 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9207 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9209 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9210 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9211 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9213 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2015-9216 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2015-9217 | 2018-04-18 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2015-9218 | 2018-04-18 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2015-9222 | 2018-04-18 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2015-9224 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10406 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10407 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10409 | 2018-04-18 | 2024-11-21 | 8.1 | 9.3 | Likely |
| CVE-2016-10410 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10411 | 2018-04-18 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2016-10412 | 2018-04-18 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2016-10414 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10415 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10416 | 2018-04-18 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2016-10417 | 2018-04-18 | 2024-11-21 | 8.1 | 9.3 | Likely |
| CVE-2016-10418 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10419 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10420 | 2018-04-18 | 2024-11-21 | 5.5 | 7.1 | Likely |
| CVE-2016-10421 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10422 | 2018-04-18 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2016-10423 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10424 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10425 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10426 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10427 | 2018-04-18 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2016-10428 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10429 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10430 | 2018-04-18 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2016-10431 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10432 | 2018-04-18 | 2024-11-21 | 8.1 | 9.3 | Likely |
| CVE-2016-10433 | 2018-04-18 | 2024-11-21 | 8.1 | 9.3 | Likely |
| CVE-2016-10435 | 2018-04-18 | 2024-11-21 | 8.1 | 9.3 | Likely |
| CVE-2016-10436 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10437 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10438 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10439 | 2018-04-18 | 2024-11-21 | 8.1 | 9.3 | Likely |
| CVE-2016-10440 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10441 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10443 | 2018-04-18 | 2024-11-21 | 6.8 | 4.0 | Unknown |
| CVE-2016-10447 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10448 | 2018-04-18 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2016-10449 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10450 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10451 | 2018-04-18 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2016-10452 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10455 | 2018-04-18 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2016-10456 | 2018-04-18 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2016-10457 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10458 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10461 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10462 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10464 | 2018-04-18 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2016-10466 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10467 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10469 | 2018-04-18 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2016-10471 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10472 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10473 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10474 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10475 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10476 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10477 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10479 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10480 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10481 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10482 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10484 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10485 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10486 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10487 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10490 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10491 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10492 | 2018-04-18 | 2024-11-21 | 9.1 | 6.4 | Likely |
| CVE-2016-10493 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10494 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10496 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10497 | 2018-04-18 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2016-10498 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2016-10499 | 2018-04-18 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2016-10501 | 2018-04-18 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2017-11088 | 2018-07-06 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2018-11258 | 2018-07-06 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2018-11259 | 2018-07-06 | 2024-11-21 | 7.7 | 3.6 | Unknown |
| CVE-2018-5838 | 2018-07-06 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2018-5874 | 2018-07-06 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-5875 | 2018-07-06 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-5876 | 2018-07-06 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-5882 | 2018-07-06 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2018-5891 | 2018-07-06 | 2024-11-21 | 8.4 | 4.6 | Unknown |
| CVE-2018-5892 | 2018-07-06 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2018-5894 | 2018-07-06 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2017-18170 | 2018-10-23 | 2024-11-21 | 8.8 | 8.3 | Unknown |
| CVE-2017-18171 | 2018-10-23 | 2024-11-21 | 8.8 | 8.3 | Unknown |
| CVE-2017-18172 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18277 | 2018-10-23 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2017-18292 | 2018-10-23 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2017-18293 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18294 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18295 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18296 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18297 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18298 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18299 | 2018-10-23 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2017-18303 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18304 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18312 | 2018-10-23 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18124 | 2018-10-26 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18310 | 2018-10-26 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18311 | 2018-10-26 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11305 | 2018-10-26 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11821 | 2018-10-26 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11828 | 2018-10-26 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2018-11849 | 2018-10-26 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11853 | 2018-10-26 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-5866 | 2018-10-26 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-5914 | 2018-10-26 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11870 | 2018-10-29 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11871 | 2018-10-29 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18318 | 2018-11-28 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-11264 | 2018-11-28 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11921 | 2018-11-28 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-5916 | 2018-11-28 | 2024-11-21 | 6.5 | 6.1 | Unknown |
| CVE-2018-5918 | 2018-11-28 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2017-11004 | 2019-01-03 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-18141 | 2019-01-03 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18319 | 2019-01-03 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-18320 | 2019-01-03 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18322 | 2019-01-03 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-18323 | 2019-01-03 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-18324 | 2019-01-03 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-18326 | 2019-01-03 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-18327 | 2019-01-03 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-18329 | 2019-01-03 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18330 | 2019-01-03 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18332 | 2019-01-18 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-8276 | 2019-01-18 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2018-11279 | 2019-01-18 | 2024-11-21 | 8.8 | 8.3 | Unknown |
| CVE-2018-3595 | 2019-01-18 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2018-5867 | 2019-01-18 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11847 | 2019-02-11 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11888 | 2019-02-11 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11899 | 2019-02-11 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2018-13888 | 2019-02-11 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11289 | 2019-02-25 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11820 | 2019-02-25 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2018-11845 | 2019-02-25 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2018-11864 | 2019-02-25 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2018-11931 | 2019-02-25 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-13913 | 2019-02-25 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2018-11958 | 2019-04-04 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2018-11966 | 2019-04-04 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-15841 | 2019-05-06 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2017-18157 | 2019-05-06 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18274 | 2019-05-06 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18275 | 2019-05-06 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2017-18278 | 2019-05-06 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2017-18279 | 2019-05-06 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11271 | 2019-05-24 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2018-11953 | 2019-05-24 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-11967 | 2019-05-24 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-11976 | 2019-05-24 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2018-13886 | 2019-05-24 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-13895 | 2019-05-24 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-13925 | 2019-05-24 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2019-2244 | 2019-05-24 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2019-2247 | 2019-05-24 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2019-2248 | 2019-05-24 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2017-8252 | 2019-06-14 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2018-11939 | 2019-06-14 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2018-11955 | 2019-06-14 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2018-13901 | 2019-06-14 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2018-13902 | 2019-06-14 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2018-13906 | 2019-06-14 | 2024-11-21 | 9.1 | 6.4 | Likely |
| CVE-2018-13907 | 2019-06-14 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2018-13908 | 2019-06-14 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2018-13910 | 2019-06-14 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-13911 | 2019-06-14 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2018-5903 | 2019-06-14 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-5913 | 2019-06-14 | 2024-11-21 | 7.8 | 7.2 | Unknown |
| CVE-2018-13924 | 2019-07-22 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2019-2261 | 2019-07-22 | 2024-11-21 | 5.5 | 4.9 | Unknown |
| CVE-2018-13897 | 2019-07-25 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-2236 | 2019-07-25 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2019-2239 | 2019-07-25 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2019-2254 | 2019-07-25 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2019-2263 | 2019-07-25 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2019-2272 | 2019-07-25 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2019-2273 | 2019-07-25 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2019-2290 | 2019-07-25 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2019-10508 | 2019-09-30 | 2024-11-21 | 7.8 | 4.6 | Unknown |
| CVE-2019-2294 | 2019-09-30 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2019-10504 | 2019-11-06 | 2024-11-21 | 6.5 | 5.0 | Likely |
| CVE-2019-10505 | 2019-11-06 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2019-2258 | 2019-11-06 | 2024-11-21 | 9.8 | 10.0 | Likely |
| CVE-2019-2275 | 2019-11-06 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-9711 | 2024-11-22 | 2024-11-25 | 6.7 | - | - |
| CVE-2018-11952 | 2024-11-26 | 2025-01-09 | 8.4 | - | - |
| CVE-2018-5852 | 2024-11-26 | 2025-01-09 | 8.4 | - | - |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records for qualcomm sd_652_firmware by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and structuring the data for rapid analysis and asset correlation. For every vulnerability listed, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference information to enable organizations to prioritize patching and risk assessment efficiently. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for vulnerability management and security operations.