This page was not yet optimized for use on mobile devices.
Qualcomm SM4350 Firmware
Configuration details
| CPE title | Qualcomm SM4350 Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:sm4350_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
68 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2020-11165 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11178 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11182 | CRITICAL | 9.8 | 09.06.2021 | |
| CVE-2020-11194 | HIGH | 7.8 | 22.02.2021 | |
| CVE-2020-11195 | HIGH | 7.8 | 22.02.2021 | |
| CVE-2020-11198 | MEDIUM | 6.7 | 22.02.2021 | |
| CVE-2020-11204 | HIGH | 7.8 | 22.02.2021 | |
| CVE-2020-11238 | HIGH | 7.5 | 09.06.2021 | |
| CVE-2020-11239 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11241 | HIGH | 7.5 | 09.06.2021 | |
| CVE-2020-11250 | HIGH | 7.0 | 09.06.2021 | |
| CVE-2020-11260 | HIGH | 8.4 | 09.06.2021 | |
| CVE-2020-11261 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11262 | HIGH | 7.0 | 09.06.2021 | |
| CVE-2020-11270 | HIGH | 7.5 | 22.02.2021 | |
| CVE-2020-11275 | CRITICAL | 9.1 | 22.02.2021 | |
| CVE-2020-11276 | CRITICAL | 9.1 | 22.02.2021 | |
| CVE-2020-11277 | HIGH | 7.4 | 22.02.2021 | |
| CVE-2020-11278 | HIGH | 7.5 | 22.02.2021 | |
| CVE-2020-11280 | HIGH | 7.5 | 22.02.2021 | |
| CVE-2020-11281 | HIGH | 7.5 | 22.02.2021 | |
| CVE-2020-11296 | HIGH | 7.5 | 22.02.2021 | |
| CVE-2020-3664 | MEDIUM | 6.0 | 22.02.2021 | |
| CVE-2022-22060 | HIGH | 7.5 | 06.06.2023 | |
| CVE-2022-22076 | MEDIUM | 5.5 | 06.06.2023 | |
| CVE-2022-33230 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2022-33231 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2022-33251 | HIGH | 7.5 | 06.06.2023 | |
| CVE-2022-33264 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2022-33270 | MEDIUM | 5.9 | 13.04.2023 | |
| CVE-2022-33275 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2022-33289 | MEDIUM | 6.8 | 13.04.2023 | |
| CVE-2022-33296 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2022-33298 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2022-33302 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2022-33305 | HIGH | 7.5 | 02.05.2023 | |
| CVE-2022-34144 | HIGH | 7.5 | 02.05.2023 | |
| CVE-2022-40503 | HIGH | 7.5 | 13.04.2023 | |
| CVE-2022-40504 | HIGH | 7.5 | 02.05.2023 | |
| CVE-2022-40507 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2022-40508 | HIGH | 7.5 | 02.05.2023 | |
| CVE-2022-40521 | HIGH | 7.5 | 06.06.2023 | |
| CVE-2022-40523 | MEDIUM | 5.5 | 06.06.2023 | |
| CVE-2022-40529 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2022-40532 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2022-40536 | HIGH | 7.5 | 06.06.2023 | |
| CVE-2023-21628 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2023-21656 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2023-21657 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2023-21659 | HIGH | 7.5 | 06.06.2023 | |
| CVE-2023-21665 | HIGH | 7.8 | 02.05.2023 | |
| CVE-2023-21670 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2023-28540 | HIGH | 7.5 | 03.10.2023 | |
| CVE-2023-28555 | HIGH | 7.5 | 08.08.2023 | |
| CVE-2023-28560 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-33018 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-33022 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-33027 | HIGH | 7.5 | 03.10.2023 | |
| CVE-2023-33029 | HIGH | 7.8 | 03.10.2023 | |
| CVE-2023-33031 | HIGH | 7.8 | 07.11.2023 | |
| CVE-2023-33035 | HIGH | 7.8 | 03.10.2023 | |
| CVE-2023-33042 | HIGH | 7.5 | 05.12.2023 | |
| CVE-2023-33043 | HIGH | 7.5 | 05.12.2023 | |
| CVE-2023-33044 | HIGH | 7.5 | 05.12.2023 | |
| CVE-2023-33054 | CRITICAL | 9.1 | 05.12.2023 | |
| CVE-2023-33059 | HIGH | 7.8 | 07.11.2023 | |
| CVE-2023-33063 | HIGH | 7.8 | 05.12.2023 | |
| CVE-2023-33080 | HIGH | 7.5 | 05.12.2023 |
Showing 5 out of 68.
Matched certificates
This CPE has no matched certificates.