This page was not yet optimized for use on mobile devices.
Qualcomm MSM8905 Firmware
Configuration details
| CPE title | Qualcomm MSM8905 Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:msm8905_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
159 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2018-13916 | HIGH | 7.8 | 21.11.2019 | |
| CVE-2019-10482 | MEDIUM | 5.9 | 18.12.2019 | |
| CVE-2019-10483 | MEDIUM | 5.5 | 16.04.2020 | |
| CVE-2019-10485 | HIGH | 7.5 | 12.12.2019 | |
| CVE-2019-10486 | HIGH | 7.0 | 21.11.2019 | |
| CVE-2019-10487 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10490 | MEDIUM | 5.5 | 21.11.2019 | |
| CVE-2019-10493 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-10500 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10503 | HIGH | 7.8 | 21.11.2019 | |
| CVE-2019-10511 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-10513 | MEDIUM | 5.5 | 18.12.2019 | |
| CVE-2019-10516 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10518 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10525 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10527 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-10532 | CRITICAL | 9.8 | 21.01.2020 | |
| CVE-2019-10544 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10548 | HIGH | 7.8 | 21.01.2020 | |
| CVE-2019-10549 | HIGH | 7.5 | 05.03.2020 | |
| CVE-2019-10550 | CRITICAL | 9.1 | 05.03.2020 | |
| 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-10559 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-10561 | MEDIUM | 5.5 | 21.01.2020 | |
| CVE-2019-10565 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-10566 | HIGH | 7.8 | 21.11.2019 | |
| CVE-2019-10572 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-10574 | HIGH | 7.1 | 16.04.2020 | |
| CVE-2019-10577 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10579 | CRITICAL | 9.1 | 21.01.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-10590 | CRITICAL | 9.8 | 07.02.2020 | |
| CVE-2019-10591 | HIGH | 7.5 | 05.03.2020 | |
| CVE-2019-10593 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10594 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10607 | HIGH | 7.8 | 18.12.2019 | |
| CVE-2019-10608 | MEDIUM | 5.5 | 16.04.2020 | |
| CVE-2019-10609 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-10610 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-10611 | CRITICAL | 9.8 | 21.01.2020 | |
| CVE-2019-10615 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-10616 | MEDIUM | 5.5 | 05.03.2020 | |
| CVE-2019-13994 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-13995 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-13998 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-13999 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-14000 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14001 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-14003 | HIGH | 7.5 | 21.01.2020 | |
| CVE-2019-14004 | CRITICAL | 9.8 | 21.01.2020 | |
| CVE-2019-14005 | CRITICAL | 9.8 | 21.01.2020 | |
| CVE-2019-14006 | CRITICAL | 9.8 | 21.01.2020 | |
| CVE-2019-14007 | MEDIUM | 5.5 | 16.04.2020 | |
| CVE-2019-14009 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-14011 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14012 | HIGH | 7.5 | 16.04.2020 | |
| CVE-2019-14013 | CRITICAL | 9.8 | 21.01.2020 | |
| CVE-2019-14016 | CRITICAL | 9.8 | 21.01.2020 | |
| CVE-2019-14017 | CRITICAL | 9.8 | 21.01.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-14021 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-14022 | HIGH | 7.5 | 16.04.2020 | |
| CVE-2019-14032 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14033 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14037 | HIGH | 7.8 | 30.07.2020 | |
| CVE-2019-14038 | HIGH | 7.1 | 02.06.2020 | |
| CVE-2019-14039 | HIGH | 7.1 | 02.06.2020 | |
| CVE-2019-14040 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-14041 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-14050 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14052 | CRITICAL | 9.8 | 08.09.2020 | |
| CVE-2019-14053 | HIGH | 7.1 | 02.06.2020 | |
| CVE-2019-14055 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-14057 | CRITICAL | 9.1 | 07.02.2020 | |
| CVE-2019-14061 | HIGH | 7.5 | 05.03.2020 | |
| CVE-2019-14062 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2019-14065 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-14068 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14070 | HIGH | 7.0 | 16.04.2020 | |
| CVE-2019-14073 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2019-14074 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-14076 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2019-14080 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2019-14094 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2019-14095 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-14101 | HIGH | 7.1 | 30.07.2020 | |
| CVE-2019-14115 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2019-14127 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-2242 | CRITICAL | 9.8 | 18.12.2019 | |
| CVE-2019-2271 | CRITICAL | 9.8 | 21.11.2019 | |
| CVE-2019-2288 | HIGH | 7.8 | 12.12.2019 | |
| CVE-2019-2289 | CRITICAL | 9.8 | 21.11.2019 | |
| CVE-2019-2295 | MEDIUM | 5.5 | 21.11.2019 | |
| CVE-2019-2297 | HIGH | 7.8 | 21.11.2019 | |
| CVE-2019-2302 | CRITICAL | 9.8 | 06.11.2019 | |
| CVE-2019-2303 | CRITICAL | 9.8 | 21.11.2019 | |
| CVE-2019-2315 | HIGH | 7.8 | 21.11.2019 | |
| CVE-2019-2317 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-2320 | CRITICAL | 9.8 | 12.12.2019 | |
| CVE-2019-2321 | HIGH | 7.8 | 12.12.2019 | |
| CVE-2019-2335 | HIGH | 7.5 | 21.11.2019 | |
| CVE-2019-2337 | HIGH | 7.5 | 12.12.2019 | |
| CVE-2020-11115 | HIGH | 7.5 | 08.09.2020 | |
| CVE-2020-11116 | CRITICAL | 9.8 | 08.09.2020 | |
| CVE-2020-11118 | HIGH | 7.5 | 08.09.2020 | |
| CVE-2020-11123 | MEDIUM | 5.5 | 12.11.2020 | |
| CVE-2020-11125 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-11132 | HIGH | 7.1 | 12.11.2020 | |
| CVE-2020-11157 | HIGH | 7.5 | 02.11.2020 | |
| CVE-2020-11174 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-11193 | CRITICAL | 9.8 | 12.11.2020 | |
| CVE-2020-11196 | CRITICAL | 9.8 | 12.11.2020 | |
| CVE-2020-3614 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2020-3619 | HIGH | 7.0 | 08.09.2020 | |
| CVE-2020-3620 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2020-3621 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2020-3622 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-3624 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-3626 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2020-3633 | CRITICAL | 9.8 | 02.06.2020 | |
| CVE-2020-3634 | CRITICAL | 9.1 | 09.09.2020 | |
| CVE-2020-3639 | CRITICAL | 9.8 | 12.11.2020 | |
| CVE-2020-3641 | CRITICAL | 9.8 | 02.06.2020 | |
| CVE-2020-3643 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2020-3644 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2020-3651 | HIGH | 7.5 | 16.04.2020 | |
| CVE-2020-3654 | CRITICAL | 9.8 | 02.11.2020 | |
| CVE-2020-3657 | CRITICAL | 9.8 | 02.11.2020 | |
| CVE-2020-3658 | CRITICAL | 9.1 | 22.06.2020 | |
| CVE-2020-3660 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2020-3661 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2020-3663 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2020-3670 | CRITICAL | 9.1 | 02.11.2020 | |
| CVE-2020-3673 | CRITICAL | 9.8 | 02.11.2020 | |
| CVE-2020-3684 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-3688 | CRITICAL | 9.8 | 30.07.2020 | |
| CVE-2020-3696 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-3698 | CRITICAL | 9.8 | 30.07.2020 | |
| CVE-2020-3699 | CRITICAL | 9.8 | 30.07.2020 | |
| CVE-2020-3703 | CRITICAL | 9.8 | 02.11.2020 | |
| CVE-2022-22076 | MEDIUM | 5.5 | 06.06.2023 | |
| CVE-2022-33264 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2022-40507 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2022-40521 | HIGH | 7.5 | 06.06.2023 | |
| CVE-2023-21670 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2023-28540 | HIGH | 7.5 | 03.10.2023 | |
| CVE-2023-33017 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-33018 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-33031 | HIGH | 7.8 | 07.11.2023 | |
| CVE-2023-33059 | HIGH | 7.8 | 07.11.2023 | |
| CVE-2023-33063 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-33070 | MEDIUM | 5.5 | 05.12.2023 |
Showing 5 out of 159.
Matched certificates
This CPE has no matched certificates.