Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-2462
|
High
|
|
May 9, 2016
|
== 6.0.1
== 6.0
|
CVE-2016-4477
|
High
|
|
May 9, 2016
|
== 5.0.2
== 6.0.1
== 6.0
== 4.4.4
== 5.1.1
|
CVE-2016-2059
|
High
|
|
May 5, 2016
|
<= 7.0
|
CVE-2016-2107
|
Medium
|
|
May 5, 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
|
CVE-2016-2108
|
Critical
|
|
May 5, 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-0774
|
Medium
|
|
Apr 27, 2016
|
<= 6.0.1
|
CVE-2016-0834
|
High
|
|
Apr 18, 2016
|
== 6.0.1
== 6.0
|
CVE-2016-0835
|
Critical
|
|
Apr 18, 2016
|
== 6.0.1
== 6.0
|
CVE-2016-0836
|
High
|
|
Apr 18, 2016
|
== 6.0.1
== 6.0
|
CVE-2016-0837
|
Critical
|
|
Apr 18, 2016
|
== 5.1.0
== 4.2
== 4.1
== 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
== 4.2.2
== 4.3.1
== 4.4.2
== 5.1
== 4.1.2
|