| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2017-15318 | 2017-12-22 | 2025-04-20 | 7.5 | 7.8 | Likely |
| CVE-2017-15319 | 2017-12-22 | 2025-04-20 | 7.5 | 7.8 | Likely |
| CVE-2017-15320 | 2017-12-22 | 2025-04-20 | 7.5 | 7.8 | Likely |
| CVE-2017-15331 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15332 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15334 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15335 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15336 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15337 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15338 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15339 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15341 | 2018-02-15 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-15350 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15353 | 2018-02-15 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-15354 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15355 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-15356 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17151 | 2018-02-15 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17182 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17183 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17184 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17185 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17186 | 2018-02-15 | 2024-11-21 | 5.4 | 5.5 | Likely |
| CVE-2017-17187 | 2018-02-15 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17283 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17284 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17288 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17289 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17291 | 2018-02-15 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17292 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17293 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17294 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17295 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17296 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17297 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17298 | 2018-02-15 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17302 | 2018-02-15 | 2024-11-21 | 3.3 | 2.1 | Unknown |
| CVE-2017-17134 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17135 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17136 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17137 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17138 | 2018-03-05 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17142 | 2018-03-05 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17143 | 2018-03-05 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17144 | 2018-03-05 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17150 | 2018-03-09 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17199 | 2018-03-09 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17200 | 2018-03-09 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17216 | 2018-03-09 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17217 | 2018-03-09 | 2024-11-21 | 5.9 | 4.3 | Likely |
| CVE-2017-17218 | 2018-03-09 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17219 | 2018-03-09 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17220 | 2018-03-09 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17281 | 2018-03-09 | 2024-11-21 | 4.3 | 4.0 | Likely |
| CVE-2017-17303 | 2018-03-09 | 2024-11-21 | 4.9 | 4.0 | Likely |
| CVE-2017-15314 | 2018-03-09 | 2024-11-21 | 5.5 | 2.1 | Unknown |
| CVE-2017-17282 | 2018-03-09 | 2024-11-21 | 3.1 | 2.9 | Unknown |
| CVE-2017-17308 | 2018-04-11 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17310 | 2018-04-19 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17251 | 2018-04-24 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17252 | 2018-04-24 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17253 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17254 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17255 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17256 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17257 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17258 | 2018-04-24 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2017-17314 | 2018-04-30 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2017-17315 | 2018-05-24 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17316 | 2018-07-02 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2017-17317 | 2018-07-02 | 2024-11-21 | 3.7 | 4.3 | Likely |
| CVE-2019-19413 | 2020-01-21 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2019-19414 | 2020-01-21 | 2024-11-21 | 7.5 | 7.8 | Likely |
| CVE-2019-19415 | 2020-07-08 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-19416 | 2020-07-08 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-19417 | 2020-07-08 | 2024-11-21 | 7.5 | 5.0 | Likely |