Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-0705
|
Critical
|
|
Mar 3, 2016
|
== 4.0
== 4.0.1
== 4.0.2
== 4.0.3
== 4.0.4
== 4.1
== 4.1.2
== 4.2
== 4.2.1
== 4.2.2
== 4.3
== 4.3.1
== 4.4
== 4.4.1
== 4.4.2
== 4.4.3
== 5.0
== 5.0.1
== 5.1
== 5.1.0
== 6.0
== 6.0.1
|
CVE-2016-0728
|
High
|
|
Feb 8, 2016
|
== 4.0
== 4.0.1
== 4.0.2
== 4.0.3
== 4.0.4
== 4.1
== 4.1.2
== 4.2
== 4.2.1
== 4.2.2
== 4.3
== 4.3.1
== 4.4
== 4.4.1
== 4.4.2
== 4.4.3
== 5.0
== 5.0.1
== 5.0.2
== 5.1
== 5.1.0
== 5.1.1
== 6.0
== 6.0.1
|
CVE-2016-0801
|
Critical
|
|
Feb 7, 2016
|
== 4.4.4
== 5.0
== 5.1.1
== 6.0
== 6.0.1
|
CVE-2016-0802
|
High
|
|
Feb 7, 2016
|
== 4.4.4
== 5.0
== 5.1.1
== 6.0
== 6.0.1
|
CVE-2016-0803
|
Critical
|
|
Feb 7, 2016
|
== 5.1.0
== 4.2
== 4.1
== 5.0.2
== 6.0.1
== 6.0
== 4.0.2
== 4.4.3
== 4.0.4
== 4.3
== 4.0.1
== 4.4.4
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.4
== 4.4.1
== 5.1.1
== 4.2.2
== 4.3.1
== 4.4.2
== 5.1
== 4.1.2
|
CVE-2016-0804
|
Critical
|
|
Feb 7, 2016
|
== 5.1.0
== 5.0.2
== 6.0.1
== 6.0
== 5.0.1
== 5.0
== 5.1.1
== 5.1
|
CVE-2016-0805
|
High
|
|
Feb 7, 2016
|
== 5.1.0
== 4.2
== 4.1
== 5.0.2
== 6.0.1
== 6.0
== 4.0.2
== 4.4.3
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.4
== 4.4.1
== 5.1.1
== 4.2.2
== 4.3.1
== 4.4.2
== 5.1
== 4.1.2
|
CVE-2016-0806
|
High
|
|
Feb 7, 2016
|
== 5.1.0
== 4.2
== 4.1
== 5.0.2
== 6.0.1
== 6.0
== 4.0.2
== 4.4.3
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.4
== 4.4.1
== 5.1.1
== 4.2.2
== 4.3.1
== 4.4.2
== 5.1
== 4.1.2
|
CVE-2016-0807
|
High
|
|
Feb 7, 2016
|
== 6.0.1
== 6.0
|
CVE-2016-0808
|
Medium
|
|
Feb 7, 2016
|
== 5.1.0
== 5.0.2
== 6.0.1
== 6.0
== 5.0.1
== 5.0
== 5.1.1
== 5.1
|