ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
---|---|---|---|---|---|
CVE-2017-11568 | 2017-07-23 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-11569 | 2017-07-23 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-11570 | 2017-07-23 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-11571 | 2017-07-23 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-11572 | 2017-07-23 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-11573 | 2017-07-23 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-11574 | 2017-07-23 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-11575 | 2017-07-23 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-11576 | 2017-07-23 | 2025-04-20 | 5.5 | 4.3 | Likely |
CVE-2017-11577 | 2017-07-23 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-17521 | 2017-12-14 | 2025-04-20 | 8.8 | 6.8 | Likely |
CVE-2019-15785 | 2019-08-29 | 2024-11-21 | 9.8 | 7.5 | Likely |
CVE-2020-5395 | 2020-01-03 | 2024-11-21 | 8.8 | 6.8 | Likely |
CVE-2020-5496 | 2020-01-03 | 2024-11-21 | 8.8 | 6.8 | Likely |
CVE-2020-25690 | 2021-02-23 | 2024-11-21 | 8.8 | 6.8 | Likely |
CVE-2024-25081 | 2024-02-26 | 2025-04-23 | 4.2 | - | - |
CVE-2024-25082 | 2024-02-26 | 2025-04-23 | 6.5 | - | - |