| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2017-15613 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15614 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15615 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15616 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15617 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15618 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15619 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15620 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15621 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15622 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15623 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15624 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15625 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15626 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15627 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15628 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15629 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15630 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15631 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15632 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15633 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15634 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15635 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15636 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |
| CVE-2017-15637 | 2018-01-11 | 2024-11-21 | 7.2 | 9.0 | Likely |