This page was not yet optimized for use on mobile devices.
Qualcomm MDM9615 Firmware
Configuration details
| CPE title | Qualcomm MDM9615 Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:mdm9615_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
154 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| 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-10057 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-10059 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-9989 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2014-9990 | 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-9137 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2015-9139 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9143 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2015-9144 | 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-9209 | 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-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-10412 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10416 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10421 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10427 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10448 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10455 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10456 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10459 | HIGH | 7.5 | 18.04.2018 | |
| CVE-2016-10479 | CRITICAL | 9.8 | 18.04.2018 | |
| CVE-2016-10492 | CRITICAL | 9.1 | 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-18136 | CRITICAL | 9.8 | 11.04.2018 | |
| CVE-2017-18319 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18322 | MEDIUM | 5.5 | 03.01.2019 | |
| CVE-2017-18323 | 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-2017-8252 | MEDIUM | 5.5 | 14.06.2019 | |
| CVE-2018-11267 | HIGH | 7.8 | 20.09.2018 | |
| 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-13886 | CRITICAL | 9.8 | 24.05.2019 | |
| CVE-2018-13902 | HIGH | 7.5 | 14.06.2019 | |
| CVE-2018-13911 | CRITICAL | 9.8 | 14.06.2019 | |
| CVE-2018-13924 | CRITICAL | 9.8 | 22.07.2019 | |
| CVE-2018-5839 | HIGH | 7.1 | 25.02.2019 | |
| CVE-2018-5916 | MEDIUM | 6.5 | 28.11.2018 | |
| CVE-2019-10480 | HIGH | 7.8 | 18.12.2019 | |
| 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-10511 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-10525 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10542 | CRITICAL | 9.8 | 06.11.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-10595 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10607 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10609 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-10610 | CRITICAL | 9.1 | 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-14036 | HIGH | 7.8 | 21.01.2020 | |
| CVE-2019-14052 | CRITICAL | 9.8 | 08.09.2020 | |
| CVE-2019-14070 | HIGH | 7.0 | 16.04.2020 | |
| CVE-2019-14073 | CRITICAL | 9.8 | 22.06.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-2324 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2331 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2332 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2335 | HIGH | 7.5 | 21.11.2019 | |
| CVE-2020-11119 | HIGH | 7.5 | 21.01.2021 | |
| 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-11171 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11177 | HIGH | 8.8 | 22.02.2021 | |
| CVE-2020-11191 | CRITICAL | 9.1 | 07.04.2021 | |
| CVE-2020-11235 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11251 | CRITICAL | 9.1 | 07.04.2021 | |
| CVE-2020-11269 | HIGH | 8.8 | 22.02.2021 | |
| CVE-2020-11275 | CRITICAL | 9.1 | 22.02.2021 | |
| CVE-2020-11276 | CRITICAL | 9.1 | 22.02.2021 | |
| CVE-2020-11279 | CRITICAL | 9.8 | 07.05.2021 | |
| CVE-2020-11292 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11296 | HIGH | 7.5 | 22.02.2021 | |
| CVE-2020-11301 | HIGH | 7.5 | 08.09.2021 | |
| CVE-2020-11303 | MEDIUM | 5.0 | 20.10.2021 | |
| CVE-2020-3624 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-3665 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2021-1916 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1920 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1955 | HIGH | 7.5 | 13.07.2021 | |
| CVE-2021-1972 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1973 | HIGH | 7.2 | 12.11.2021 | |
| CVE-2021-1975 | HIGH | 10.0 | 12.11.2021 | |
| CVE-2021-30260 | HIGH | 7.8 | 17.09.2021 | |
| CVE-2021-30261 | HIGH | 7.8 | 17.09.2021 | |
| CVE-2021-30268 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30270 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30273 | HIGH | 7.5 | 03.01.2022 | |
| CVE-2021-30284 | CRITICAL | 9.1 | 12.11.2021 | |
| CVE-2021-30293 | HIGH | 7.5 | 03.01.2022 | |
| CVE-2021-30344 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2021-35115 | HIGH | 7.8 | 01.04.2022 | |
| CVE-2022-25655 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25682 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25694 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25718 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25720 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25736 | HIGH | 7.5 | 19.10.2022 | |
| CVE-2022-25748 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25749 | HIGH | 7.5 | 19.10.2022 | |
| CVE-2022-33213 | HIGH | 8.8 | 10.03.2023 | |
| CVE-2022-33238 | HIGH | 7.5 | 13.12.2022 | |
| CVE-2022-33239 | HIGH | 7.5 | 15.11.2022 | |
| CVE-2022-33264 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2022-33285 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-33286 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-33289 | MEDIUM | 6.8 | 13.04.2023 | |
| CVE-2022-33302 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2022-40512 | HIGH | 7.5 | 12.02.2023 | |
| CVE-2022-40521 | HIGH | 7.5 | 06.06.2023 | |
| CVE-2022-40532 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2023-21628 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2023-24848 | HIGH | 7.5 | 03.10.2023 | |
| CVE-2023-24849 | HIGH | 7.5 | 03.10.2023 | |
| CVE-2023-28565 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-33018 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-33066 | HIGH | 7.8 | 04.03.2024 | |
| CVE-2023-33080 | HIGH | 7.5 | 05.12.2023 | |
| CVE-2023-43551 | HIGH | 7.5 | 03.06.2024 | |
| CVE-2024-33051 | HIGH | 7.5 | 02.09.2024 |
Showing 5 out of 154.
Matched certificates
This CPE has no matched certificates.