Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-2416
|
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
|
CVE-2016-2417
|
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
|
CVE-2016-2418
|
Critical
|
|
Apr 18, 2016
|
== 6.0.1
== 6.0
|
CVE-2016-2419
|
Critical
|
|
Apr 18, 2016
|
== 6.0.1
== 6.0
|
CVE-2016-2420
|
High
|
|
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
|
CVE-2016-2421
|
Medium
|
|
Apr 18, 2016
|
== 5.1.0
== 6.0.1
== 6.0
== 5.1
|
CVE-2016-2422
|
High
|
|
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
|
CVE-2016-2423
|
Medium
|
|
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
|
CVE-2016-2424
|
Medium
|
|
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
|
CVE-2016-2425
|
Medium
|
|
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
|