This page was not yet optimized for use on mobile devices.
Qualcomm SNAPDRAGON AR2 GEN 1 FIRMWARE -
Configuration details
| CPE title | Qualcomm SNAPDRAGON AR2 GEN 1 FIRMWARE - |
|---|---|
| URI | cpe:2.3:o:qualcomm:snapdragon_ar2_gen_1_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
71 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2023-21672 | HIGH | 7.8 | 04.07.2023 | |
| CVE-2023-22386 | HIGH | 7.8 | 04.07.2023 | |
| CVE-2023-22387 | HIGH | 7.8 | 04.07.2023 | |
| CVE-2023-24851 | HIGH | 7.8 | 04.07.2023 | |
| CVE-2023-24854 | HIGH | 7.8 | 04.07.2023 | |
| CVE-2023-28542 | HIGH | 7.8 | 04.07.2023 | |
| CVE-2023-28547 | HIGH | 7.8 | 01.04.2024 | |
| CVE-2023-28567 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-28573 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-28578 | HIGH | 7.8 | 04.03.2024 | |
| CVE-2023-28581 | CRITICAL | 9.8 | 05.09.2023 | |
| CVE-2023-28584 | HIGH | 7.5 | 05.09.2023 | |
| CVE-2023-33015 | HIGH | 7.5 | 05.09.2023 | |
| CVE-2023-33016 | HIGH | 7.5 | 05.09.2023 | |
| CVE-2023-33023 | HIGH | 7.8 | 01.04.2024 | |
| CVE-2023-33115 | HIGH | 7.8 | 01.04.2024 | |
| CVE-2023-33119 | HIGH | 7.0 | 06.05.2024 | |
| CVE-2023-43530 | HIGH | 7.8 | 06.05.2024 | |
| CVE-2023-43531 | HIGH | 7.8 | 06.05.2024 | |
| CVE-2023-43537 | HIGH | 7.5 | 03.06.2024 | |
| CVE-2023-43538 | HIGH | 7.8 | 03.06.2024 | |
| CVE-2023-43539 | HIGH | 7.5 | 04.03.2024 | |
| CVE-2023-43542 | HIGH | 7.8 | 03.06.2024 | |
| CVE-2023-43549 | HIGH | 7.8 | 04.03.2024 | |
| CVE-2023-43550 | HIGH | 7.8 | 04.03.2024 | |
| CVE-2023-43552 | CRITICAL | 9.8 | 04.03.2024 | |
| CVE-2023-43553 | CRITICAL | 9.8 | 04.03.2024 | |
| CVE-2023-43556 | HIGH | 8.8 | 03.06.2024 | |
| CVE-2024-21463 | CRITICAL | 9.8 | 01.04.2024 | |
| CVE-2024-21471 | HIGH | 7.8 | 06.05.2024 | |
| CVE-2024-21475 | HIGH | 7.8 | 06.05.2024 | |
| CVE-2024-21477 | HIGH | 7.5 | 06.05.2024 | |
| CVE-2024-21480 | CRITICAL | 9.8 | 06.05.2024 | |
| CVE-2024-23351 | HIGH | 7.8 | 06.05.2024 | |
| CVE-2024-23354 | HIGH | 7.8 | 06.05.2024 | |
| CVE-2024-23363 | HIGH | 7.5 | 03.06.2024 | |
| CVE-2024-33038 | HIGH | 7.8 | 02.09.2024 | |
| CVE-2024-33045 | HIGH | 7.8 | 02.09.2024 | |
| CVE-2024-33048 | HIGH | 7.5 | 02.09.2024 | |
| CVE-2024-33050 | HIGH | 7.5 | 02.09.2024 | |
| CVE-2024-33051 | HIGH | 7.5 | 02.09.2024 | |
| CVE-2024-33055 | HIGH | 7.8 | 06.01.2025 | |
| CVE-2024-33057 | HIGH | 7.5 | 02.09.2024 | |
| CVE-2024-33060 | HIGH | 7.8 | 02.09.2024 | |
| CVE-2024-38402 | HIGH | 7.8 | 02.09.2024 | |
| CVE-2024-38420 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-43051 | MEDIUM | 5.5 | 03.03.2025 | |
| CVE-2024-45553 | HIGH | 7.8 | 06.01.2025 | |
| CVE-2024-45580 | HIGH | 7.8 | 03.03.2025 | |
| CVE-2024-49833 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-49834 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-49838 | HIGH | 7.5 | 03.02.2025 | |
| CVE-2024-49839 | CRITICAL | 9.8 | 03.02.2025 | |
| CVE-2024-49841 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-49842 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-53009 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2024-53014 | HIGH | 7.8 | 03.03.2025 | |
| CVE-2024-53024 | HIGH | 7.8 | 03.03.2025 | |
| CVE-2024-53027 | HIGH | 7.5 | 03.03.2025 | |
| CVE-2025-21422 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-21432 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-21433 | MEDIUM | 5.5 | 08.07.2025 | |
| CVE-2025-21446 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-21449 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-21454 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-21459 | HIGH | 7.5 | 06.05.2025 | |
| CVE-2025-21468 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2025-27042 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-27057 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-27061 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-47366 | HIGH | 7.8 | 02.02.2026 |
Showing 5 out of 71.
Matched certificates
This CPE has no matched certificates.