This page was not yet optimized for use on mobile devices.
Qualcomm SDW2500 Firmware
Configuration details
| CPE title | Qualcomm SDW2500 Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:sdw2500_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
113 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2020-11123 | MEDIUM | 5.5 | 12.11.2020 | |
| CVE-2020-11166 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11168 | CRITICAL | 9.8 | 12.11.2020 | |
| 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-11188 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11189 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11190 | CRITICAL | 9.1 | 17.03.2021 | |
| CVE-2020-11191 | CRITICAL | 9.1 | 07.04.2021 | |
| CVE-2020-11192 | CRITICAL | 9.8 | 17.03.2021 | |
| CVE-2020-11193 | CRITICAL | 9.8 | 12.11.2020 | |
| CVE-2020-11196 | CRITICAL | 9.8 | 12.11.2020 | |
| CVE-2020-11199 | MEDIUM | 5.5 | 17.03.2021 | |
| CVE-2020-11221 | MEDIUM | 5.5 | 17.03.2021 | |
| CVE-2020-11226 | HIGH | 7.5 | 17.03.2021 | |
| CVE-2020-11227 | CRITICAL | 9.8 | 17.03.2021 | |
| CVE-2020-11233 | HIGH | 7.0 | 09.06.2021 | |
| CVE-2020-11234 | HIGH | 7.8 | 07.04.2021 | |
| CVE-2020-11239 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11251 | CRITICAL | 9.1 | 07.04.2021 | |
| CVE-2020-11261 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11267 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11269 | HIGH | 8.8 | 22.02.2021 | |
| CVE-2020-11272 | CRITICAL | 9.8 | 22.02.2021 | |
| CVE-2020-11279 | CRITICAL | 9.8 | 07.05.2021 | |
| CVE-2020-11285 | CRITICAL | 9.1 | 07.05.2021 | |
| CVE-2020-11292 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11299 | CRITICAL | 9.8 | 17.03.2021 | |
| CVE-2020-11307 | CRITICAL | 9.8 | 13.07.2021 | |
| CVE-2021-1900 | HIGH | 7.0 | 09.06.2021 | |
| CVE-2021-1904 | MEDIUM | 5.5 | 08.09.2021 | |
| CVE-2021-1905 | HIGH | 7.8 | 07.05.2021 | |
| CVE-2021-1909 | HIGH | 7.8 | 09.09.2021 | |
| CVE-2021-1910 | CRITICAL | 9.8 | 07.05.2021 | |
| CVE-2021-1914 | HIGH | 7.5 | 08.09.2021 | |
| CVE-2021-1916 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1919 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1920 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-1924 | MEDIUM | 5.5 | 12.11.2021 | |
| CVE-2021-1936 | HIGH | 7.8 | 20.10.2021 | |
| CVE-2021-1949 | HIGH | 7.2 | 20.10.2021 | |
| CVE-2021-1955 | HIGH | 7.5 | 13.07.2021 | |
| CVE-2021-1959 | HIGH | 7.2 | 20.10.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-1976 | HIGH | 10.0 | 17.09.2021 | |
| CVE-2021-30254 | HIGH | 7.2 | 12.11.2021 | |
| CVE-2021-30255 | HIGH | 7.2 | 12.11.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-30271 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30272 | 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-30289 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30300 | HIGH | 7.5 | 13.01.2022 | |
| CVE-2021-30318 | HIGH | 7.8 | 11.02.2022 | |
| CVE-2021-30323 | HIGH | 7.8 | 11.02.2022 | |
| CVE-2021-30330 | HIGH | 7.5 | 13.01.2022 | |
| CVE-2021-30333 | HIGH | 7.8 | 01.04.2022 | |
| CVE-2021-30337 | HIGH | 7.8 | 03.01.2022 | |
| CVE-2021-30341 | CRITICAL | 9.8 | 14.06.2022 | |
| CVE-2021-30342 | MEDIUM | 5.9 | 14.06.2022 | |
| CVE-2021-30344 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2021-30351 | CRITICAL | 9.8 | 03.01.2022 | |
| CVE-2021-35068 | CRITICAL | 9.8 | 11.02.2022 | |
| CVE-2021-35072 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2021-35083 | CRITICAL | 9.1 | 14.06.2022 | |
| CVE-2021-35100 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2021-35104 | CRITICAL | 9.8 | 14.06.2022 | |
| CVE-2021-35105 | HIGH | 7.8 | 01.04.2022 | |
| CVE-2021-35116 | HIGH | 7.1 | 14.06.2022 | |
| CVE-2022-22058 | HIGH | 7.8 | 26.09.2022 | |
| CVE-2022-22062 | CRITICAL | 9.1 | 02.09.2022 | |
| CVE-2022-22064 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2022-22065 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2022-22074 | HIGH | 7.8 | 16.09.2022 | |
| CVE-2022-22075 | MEDIUM | 5.5 | 10.03.2023 | |
| CVE-2022-22079 | MEDIUM | 4.6 | 09.01.2023 | |
| CVE-2022-22082 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2022-22083 | HIGH | 7.5 | 14.06.2022 | |
| CVE-2022-22084 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2022-22085 | HIGH | 7.8 | 14.06.2022 | |
| CVE-2022-22086 | CRITICAL | 9.8 | 14.06.2022 | |
| CVE-2022-22087 | CRITICAL | 9.8 | 14.06.2022 | |
| CVE-2022-22088 | HIGH | 8.8 | 09.01.2023 | |
| CVE-2022-25658 | CRITICAL | 9.8 | 02.09.2022 | |
| CVE-2022-25659 | CRITICAL | 9.8 | 02.09.2022 | |
| CVE-2022-25668 | CRITICAL | 9.8 | 02.09.2022 | |
| CVE-2022-25669 | HIGH | 7.5 | 16.09.2022 | |
| CVE-2022-25670 | HIGH | 7.5 | 16.09.2022 | |
| CVE-2022-25682 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25687 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25688 | CRITICAL | 9.8 | 16.09.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-25706 | HIGH | 7.5 | 16.09.2022 | |
| CVE-2022-25718 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25719 | CRITICAL | 9.1 | 19.10.2022 | |
| CVE-2022-25720 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25724 | HIGH | 7.8 | 15.11.2022 | |
| CVE-2022-25743 | HIGH | 7.8 | 15.11.2022 | |
| CVE-2022-33213 | HIGH | 8.8 | 10.03.2023 | |
| CVE-2022-33233 | HIGH | 7.8 | 12.02.2023 | |
| CVE-2022-33248 | HIGH | 7.8 | 12.02.2023 | |
| CVE-2022-33266 | HIGH | 7.8 | 09.01.2023 | |
| CVE-2022-40510 | CRITICAL | 9.8 | 08.08.2023 | |
| CVE-2022-40515 | CRITICAL | 9.8 | 10.03.2023 | |
| CVE-2022-40537 | CRITICAL | 9.8 | 10.03.2023 |
Showing 5 out of 113.
Matched certificates
This CPE has no matched certificates.