ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
---|---|---|---|---|---|
CVE-2018-25032 | 2022-03-25 | 2025-05-06 | 7.5 | 5.0 | Likely |
CVE-2022-21426 | 2022-04-19 | 2024-11-21 | 5.3 | 5.0 | Likely |
CVE-2022-21434 | 2022-04-19 | 2024-11-21 | 5.3 | 5.0 | Likely |
CVE-2022-21443 | 2022-04-19 | 2024-11-21 | 3.7 | 4.3 | Likely |
CVE-2022-21449 | 2022-04-19 | 2024-11-21 | 7.5 | 5.0 | Likely |
CVE-2022-21476 | 2022-04-19 | 2024-11-21 | 7.5 | 5.0 | Likely |
CVE-2022-21496 | 2022-04-19 | 2024-11-21 | 5.3 | 5.0 | Likely |
CVE-2022-34169 | 2022-07-19 | 2024-11-21 | 7.5 | - | - |
CVE-2022-21540 | 2022-07-19 | 2024-11-21 | 5.3 | - | - |
CVE-2022-21541 | 2022-07-19 | 2024-11-21 | 5.9 | - | - |
CVE-2022-21549 | 2022-07-19 | 2024-11-21 | 5.3 | - | - |
CVE-2022-21618 | 2022-10-18 | 2024-11-21 | 5.3 | - | - |
CVE-2022-21619 | 2022-10-18 | 2024-11-21 | 3.7 | - | - |
CVE-2022-21624 | 2022-10-18 | 2024-11-21 | 3.7 | - | - |
CVE-2022-21626 | 2022-10-18 | 2024-11-21 | 5.3 | - | - |
CVE-2022-21628 | 2022-10-18 | 2024-11-21 | 5.3 | - | - |
CVE-2022-39399 | 2022-10-18 | 2024-11-21 | 3.7 | - | - |
CVE-2023-21830 | 2023-01-18 | 2024-11-21 | 5.3 | - | - |
CVE-2023-21835 | 2023-01-18 | 2024-11-21 | 5.3 | - | - |
CVE-2023-21843 | 2023-01-18 | 2024-11-21 | 3.7 | - | - |