Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-1459
|
Low
|
|
Jan 10, 2018
|
*
|
CVE-2016-5919
|
High
|
|
Feb 16, 2017
|
*
|
CVE-2015-5013
|
Medium
|
|
Feb 8, 2017
|
*
|
CVE-2016-3020
|
Medium
|
|
Feb 7, 2017
|
*
|
CVE-2016-2908
|
Critical
|
|
Feb 1, 2017
|
== 8.0.0.1
== 8.0.0.2
== 8.0.0.3
== 8.0.0.5
== 8.0.1.0
== 8.0.1.2
== 8.0.1.3
== 8.0.1.4
|
CVE-2016-3016
|
Low
|
|
Feb 1, 2017
|
== 8.0.0.1
== 8.0.0.2
== 8.0.0.3
== 8.0.0.5
== 8.0.1.0
== 8.0.1.2
== 8.0.1.3
== 8.0.1.4
|
CVE-2016-3017
|
High
|
|
Feb 1, 2017
|
== 8.0.0.1
== 8.0.0.2
== 8.0.0.3
== 8.0.0.5
== 8.0.1.0
== 8.0.1.2
== 8.0.1.3
== 8.0.1.4
|
CVE-2016-3021
|
Low
|
|
Feb 1, 2017
|
== 8.0.0.1
== 8.0.0.2
== 8.0.0.3
== 8.0.0.5
== 8.0.1.0
== 8.0.1.2
== 8.0.1.3
== 8.0.1.4
|
CVE-2016-3022
|
Medium
|
|
Feb 1, 2017
|
== 8.0.0.1
== 8.0.0.2
== 8.0.0.3
== 8.0.0.5
== 8.0.1.0
== 8.0.1.2
== 8.0.1.3
== 8.0.1.4
|
CVE-2016-3023
|
Medium
|
|
Feb 1, 2017
|
== 8.0.0.1
== 8.0.0.2
== 8.0.0.3
== 8.0.0.5
== 8.0.1.0
== 8.0.1.2
== 8.0.1.3
== 8.0.1.4
|