| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2017-15750 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15751 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15752 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15753 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15754 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15755 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15756 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15757 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15758 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15759 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15760 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15761 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15762 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15763 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15764 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |
| CVE-2017-15766 | 2017-10-22 | 2025-04-20 | 7.8 | 6.8 | Likely |