This page was not yet optimized for use on mobile devices.
Qualcomm QCC5100 Firmware
Configuration details
| CPE title | Qualcomm QCC5100 Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:qcc5100_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
71 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2022-22075 | MEDIUM | 5.5 | 10.03.2023 | |
| CVE-2022-22088 | HIGH | 8.8 | 09.01.2023 | |
| CVE-2022-25655 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25662 | HIGH | 7.5 | 19.10.2022 | |
| CVE-2022-25664 | MEDIUM | 5.5 | 19.10.2022 | |
| CVE-2022-25666 | MEDIUM | 6.7 | 19.10.2022 | |
| CVE-2022-25676 | MEDIUM | 5.5 | 15.11.2022 | |
| CVE-2022-25682 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25685 | HIGH | 7.5 | 13.12.2022 | |
| CVE-2022-25687 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25694 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25695 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25705 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25711 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25712 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25718 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25720 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25724 | HIGH | 7.8 | 15.11.2022 | |
| CVE-2022-25736 | HIGH | 7.5 | 19.10.2022 | |
| CVE-2022-25741 | HIGH | 7.5 | 15.11.2022 | |
| CVE-2022-25743 | HIGH | 7.8 | 15.11.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-33214 | HIGH | 7.0 | 19.10.2022 | |
| CVE-2022-33220 | MEDIUM | 5.5 | 05.09.2023 | |
| CVE-2022-33233 | HIGH | 7.8 | 12.02.2023 | |
| CVE-2022-33235 | HIGH | 7.5 | 13.12.2022 | |
| CVE-2022-33237 | HIGH | 7.5 | 15.11.2022 | |
| CVE-2022-33238 | HIGH | 7.5 | 13.12.2022 | |
| CVE-2022-33239 | HIGH | 7.5 | 15.11.2022 | |
| CVE-2022-33242 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-33243 | HIGH | 7.8 | 12.02.2023 | |
| CVE-2022-33248 | HIGH | 7.8 | 12.02.2023 | |
| CVE-2022-33255 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-33257 | HIGH | 7.0 | 10.03.2023 | |
| CVE-2022-33260 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-33266 | HIGH | 7.8 | 09.01.2023 | |
| CVE-2022-33268 | HIGH | 8.1 | 13.12.2022 | |
| CVE-2022-33271 | HIGH | 7.5 | 12.02.2023 | |
| CVE-2022-33277 | HIGH | 7.8 | 12.02.2023 | |
| CVE-2022-33278 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-33284 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-33285 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-33286 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-33300 | HIGH | 7.8 | 09.01.2023 | |
| CVE-2022-34145 | HIGH | 7.5 | 12.02.2023 | |
| CVE-2022-40510 | CRITICAL | 9.8 | 08.08.2023 | |
| CVE-2022-40512 | HIGH | 7.5 | 12.02.2023 | |
| CVE-2022-40514 | CRITICAL | 9.8 | 12.02.2023 | |
| CVE-2022-40515 | CRITICAL | 9.8 | 10.03.2023 | |
| CVE-2022-40516 | HIGH | 7.8 | 09.01.2023 | |
| CVE-2022-40517 | HIGH | 7.8 | 09.01.2023 | |
| CVE-2022-40519 | MEDIUM | 5.5 | 09.01.2023 | |
| CVE-2022-40524 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2022-40531 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-40537 | CRITICAL | 9.8 | 10.03.2023 | |
| CVE-2022-40539 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2023-21627 | HIGH | 7.8 | 08.08.2023 | |
| CVE-2023-21636 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-21644 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-21647 | MEDIUM | 6.5 | 08.08.2023 | |
| CVE-2023-21648 | HIGH | 7.8 | 08.08.2023 | |
| CVE-2023-21649 | HIGH | 7.8 | 08.08.2023 | |
| CVE-2023-21650 | HIGH | 7.8 | 08.08.2023 | |
| CVE-2023-21651 | HIGH | 7.8 | 08.08.2023 | |
| CVE-2023-21652 | HIGH | 7.1 | 08.08.2023 | |
| CVE-2023-21654 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-21655 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-21663 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-21667 | MEDIUM | 6.5 | 05.09.2023 |
Showing 5 out of 71.
Matched certificates
This CPE has no matched certificates.