This page was not yet optimized for use on mobile devices.
Qualcomm MDM9625 Firmware
Configuration details
| CPE title | Qualcomm MDM9625 Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:mdm9625_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
141 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2014-10039 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10044 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2014-10045 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10046 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10052 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10057 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10059 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10063 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2014-9989 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-9990 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-9991 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-9997 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9108 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9109 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9111 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9112 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9113 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9115 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9116 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9118 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9119 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9123 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9124 | CRITICAL | 9.1 | 18.04.2018 | |
| CVE-2015-9135 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9137 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9138 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9139 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9140 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9143 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9144 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9146 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9147 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9148 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9150 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9151 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9157 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9189 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9190 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9195 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9198 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9199 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9201 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9213 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9215 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9216 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9223 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9224 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10410 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10414 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10416 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10417 | HIGH | 8.1 | 18.04.2018 | |
| CVE-2016-10421 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10427 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10435 | HIGH | 8.1 | 18.04.2018 | |
| CVE-2016-10448 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10455 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10459 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10466 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10482 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10484 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10485 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10490 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10491 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10497 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10498 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10499 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2017-18074 | CRITICAL | 9.8 | 11.04.2018 | |
| CVE-2017-18124 | HIGH | 7.8 | 26.10.2018 | |
| CVE-2017-18319 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18322 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18324 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18326 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18329 | HIGH | 7.8 | 03.01.2019 | |
| CVE-2018-11279 | HIGH | 8.8 | 18.01.2019 | |
| CVE-2018-11945 | CRITICAL | 9.8 | 25.02.2019 | |
| CVE-2018-13885 | MEDIUM | 5.5 | 24.05.2019 | |
| CVE-2018-13924 | CRITICAL | 9.8 | 22.07.2019 | |
| CVE-2018-5839 | HIGH | 7.1 | 25.02.2019 | |
| CVE-2018-5913 | HIGH | 7.8 | 14.06.2019 | |
| CVE-2018-5916 | MEDIUM | 6.5 | 28.11.2018 | |
| CVE-2019-10485 | HIGH | 7.5 | 12.12.2019 | |
| CVE-2019-10487 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10493 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-10500 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10511 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-10516 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10525 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10551 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-10552 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10553 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10554 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10577 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10586 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10587 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10588 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-10594 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10610 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14011 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14018 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-14019 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14020 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14033 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14052 | CRITICAL | 9.8 | 08.09.2020 | |
| CVE-2019-14062 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2019-14074 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-14094 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2019-14101 | HIGH | 7.1 | 30.07.2020 | |
| CVE-2019-2242 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-2254 | CRITICAL | 9.8 | 25.07.2019 | |
| CVE-2019-2258 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2271 | CRITICAL | 9.8 | 21.11.2019 | |
| CVE-2019-2289 | CRITICAL | 9.8 | 21.11.2019 | |
| CVE-2019-2294 | CRITICAL | 9.8 | 30.09.2019 | |
| CVE-2019-2303 | CRITICAL | 9.8 | 21.11.2019 | |
| CVE-2019-2320 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-2335 | HIGH | 7.5 | 21.11.2019 | |
| CVE-2020-11159 | CRITICAL | 9.1 | 09.06.2021 | |
| CVE-2020-11166 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11170 | CRITICAL | 9.8 | 22.02.2021 | |
| CVE-2020-11177 | HIGH | 8.8 | 22.02.2021 | |
| CVE-2020-11235 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11269 | HIGH | 8.8 | 22.02.2021 | |
| CVE-2020-11276 | CRITICAL | 9.1 | 22.02.2021 | |
| CVE-2020-11279 | CRITICAL | 9.8 | 07.05.2021 | |
| CVE-2020-11285 | CRITICAL | 9.1 | 07.05.2021 | |
| CVE-2020-11292 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11296 | HIGH | 7.5 | 22.02.2021 | |
| CVE-2020-3624 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-3634 | CRITICAL | 9.1 | 09.09.2020 | |
| CVE-2020-3670 | CRITICAL | 9.1 | 02.11.2020 | |
| CVE-2021-1909 | HIGH | 7.8 | 09.09.2021 | |
| CVE-2021-1916 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1919 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1920 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1924 | MEDIUM | 5.5 | 12.11.2021 | |
| CVE-2021-30261 | HIGH | 7.8 | 17.09.2021 | |
| CVE-2021-30284 | CRITICAL | 9.1 | 12.11.2021 | |
| CVE-2021-30344 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2022-25719 | CRITICAL | 9.1 | 19.10.2022 | |
| CVE-2023-33033 | HIGH | 7.8 | 02.01.2024 | |
| CVE-2023-33066 | HIGH | 7.8 | 04.03.2024 |
Showing 5 out of 141.
Matched certificates
This CPE has no matched certificates.