Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-2477
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|
CVE-2016-2478
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|
CVE-2016-2479
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|
CVE-2016-2480
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|
CVE-2016-2481
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|
CVE-2016-2482
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|
CVE-2016-2483
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|
CVE-2016-2484
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|
CVE-2016-2485
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|
CVE-2016-2486
|
High
|
|
Jun 13, 2016
|
== 4.1.1
== 4.2
== 4.1
== 6.0.1
== 6.0
== 4.0.2
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 5.0.1
== 5.0
== 4.0.3
== 4.0
== 4.2.2
== 4.3.1
== 5.1
== 4.1.2
|