This page was not yet optimized for use on mobile devices.
Qualcomm Saipan Firmware -
Configuration details
| CPE title | Qualcomm Saipan Firmware - |
|---|---|
| URI | cpe:2.3:o:qualcomm:saipan_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
95 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2019-10527 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-10547 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-10556 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-10567 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-10577 | CRITICAL | 9.1 | 05.03.2020 | |
| CVE-2019-10580 | HIGH | 7.8 | 30.07.2020 | |
| CVE-2019-10590 | CRITICAL | 9.8 | 07.02.2020 | |
| CVE-2019-10591 | HIGH | 7.5 | 05.03.2020 | |
| CVE-2019-10596 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-10597 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2019-10604 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-10621 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-10626 | MEDIUM | 5.5 | 22.06.2020 | |
| CVE-2019-10628 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-10629 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-13992 | HIGH | 7.8 | 08.09.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-14029 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14032 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14041 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-14057 | CRITICAL | 9.1 | 07.02.2020 | |
| CVE-2019-14060 | HIGH | 7.8 | 07.02.2020 | |
| CVE-2019-14061 | HIGH | 7.5 | 05.03.2020 | |
| CVE-2019-14063 | CRITICAL | 9.1 | 07.02.2020 | |
| CVE-2019-14068 | HIGH | 7.8 | 05.03.2020 | |
| CVE-2019-14070 | HIGH | 7.0 | 16.04.2020 | |
| CVE-2019-14072 | HIGH | 7.0 | 05.03.2020 | |
| CVE-2019-14074 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-14075 | MEDIUM | 5.5 | 16.04.2020 | |
| CVE-2019-14091 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2019-14092 | MEDIUM | 5.5 | 22.06.2020 | |
| CVE-2019-14094 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2019-14095 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-14099 | HIGH | 7.8 | 30.07.2020 | |
| CVE-2019-14101 | HIGH | 7.1 | 30.07.2020 | |
| CVE-2019-14117 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-14122 | HIGH | 7.8 | 16.04.2020 | |
| CVE-2019-14127 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-14131 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-14135 | HIGH | 7.8 | 16.04.2020 | |
| 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-11120 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-11122 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2020-11124 | HIGH | 7.8 | 09.09.2020 | |
| CVE-2020-11125 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-11128 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-11129 | HIGH | 7.8 | 09.09.2020 | |
| CVE-2020-11135 | HIGH | 7.5 | 09.09.2020 | |
| CVE-2020-11162 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-11164 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-11173 | HIGH | 7.0 | 02.11.2020 | |
| CVE-2020-11174 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-3610 | HIGH | 7.8 | 02.06.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-3630 | HIGH | 7.8 | 02.06.2020 | |
| CVE-2020-3633 | CRITICAL | 9.8 | 02.06.2020 | |
| CVE-2020-3634 | CRITICAL | 9.1 | 09.09.2020 | |
| CVE-2020-3635 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2020-3640 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-3641 | CRITICAL | 9.8 | 02.06.2020 | |
| CVE-2020-3642 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2020-3646 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2020-3654 | CRITICAL | 9.8 | 02.11.2020 | |
| CVE-2020-3656 | HIGH | 7.8 | 09.09.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-3662 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2020-3663 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2020-3667 | CRITICAL | 9.8 | 08.09.2020 | |
| CVE-2020-3670 | CRITICAL | 9.1 | 02.11.2020 | |
| CVE-2020-3671 | CRITICAL | 9.8 | 30.07.2020 | |
| CVE-2020-3673 | CRITICAL | 9.8 | 02.11.2020 | |
| CVE-2020-3674 | MEDIUM | 5.5 | 09.09.2020 | |
| CVE-2020-3675 | CRITICAL | 9.8 | 08.09.2020 | |
| CVE-2020-3676 | HIGH | 7.8 | 22.06.2020 | |
| CVE-2020-3679 | MEDIUM | 5.5 | 09.09.2020 | |
| CVE-2020-3684 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-3688 | CRITICAL | 9.8 | 30.07.2020 | |
| CVE-2020-3690 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-3692 | CRITICAL | 9.8 | 02.11.2020 | |
| CVE-2020-3693 | HIGH | 7.8 | 02.11.2020 | |
| CVE-2020-3694 | 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-3701 | HIGH | 7.8 | 30.07.2020 | |
| CVE-2020-3704 | HIGH | 7.5 | 02.11.2020 |
Showing 5 out of 95.
Matched certificates
This CPE has no matched certificates.