ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
---|---|---|---|---|---|
CVE-2017-15239 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15240 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15241 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15242 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15243 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15244 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15245 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15246 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15247 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15248 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15249 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15250 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15251 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15252 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15253 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15254 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15255 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15256 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15257 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15258 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15259 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15260 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15261 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15262 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |
CVE-2017-15263 | 2017-10-11 | 2025-04-20 | 7.8 | 6.8 | Likely |