ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
---|---|---|---|---|---|
CVE-2001-0895 | 2001-11-15 | 2025-04-03 | - | 5.0 | Likely |
CVE-2005-4258 | 2005-12-15 | 2025-04-03 | - | 7.8 | Likely |
CVE-2013-1100 | 2013-02-13 | 2025-04-11 | - | 5.4 | Unknown |
CVE-2017-12231 | 2017-09-29 | 2025-04-20 | 7.5 | 7.8 | Likely |
CVE-2017-12232 | 2017-09-29 | 2025-04-20 | 6.5 | 6.1 | Unknown |
CVE-2017-12237 | 2017-09-29 | 2025-04-20 | 7.5 | 7.8 | Likely |
CVE-2017-12319 | 2018-03-27 | 2025-01-27 | 5.9 | 7.1 | Likely |
CVE-2018-0154 | 2018-03-28 | 2025-01-27 | 7.5 | 7.8 | Likely |
CVE-2018-0179 | 2018-03-28 | 2025-01-27 | 5.9 | 7.1 | Likely |
CVE-2018-0180 | 2018-03-28 | 2025-01-27 | 5.9 | 7.1 | Likely |
CVE-2021-1620 | 2021-09-23 | 2024-11-21 | 7.7 | 3.5 | Unknown |
CVE-2021-1529 | 2021-10-21 | 2024-11-21 | 7.8 | 6.9 | Unknown |
CVE-2022-20677 | 2022-04-15 | 2024-11-21 | 5.5 | 7.2 | Unknown |
CVE-2022-20678 | 2022-04-15 | 2024-11-21 | 8.6 | 7.8 | Likely |
CVE-2022-20775 | 2022-09-30 | 2024-11-21 | 7.8 | - | - |
CVE-2022-20818 | 2022-09-30 | 2024-11-21 | 7.8 | - | - |
CVE-2022-20848 | 2022-09-30 | 2024-11-21 | 8.6 | - | - |
CVE-2022-20851 | 2022-09-30 | 2024-11-21 | 5.5 | - | - |
CVE-2022-20919 | 2022-09-30 | 2024-11-21 | 8.6 | - | - |
CVE-2022-20837 | 2022-10-10 | 2024-11-21 | 8.6 | - | - |
CVE-2023-20035 | 2023-03-23 | 2024-11-21 | 7.8 | - | - |
CVE-2023-20065 | 2023-03-23 | 2024-11-21 | 7.8 | - | - |
CVE-2023-20066 | 2023-03-23 | 2024-11-21 | 6.5 | - | - |