Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-3752
|
High
|
|
Jul 11, 2016
|
== 6.0.1
== 6.0
|
CVE-2016-3753
|
High
|
|
Jul 11, 2016
|
== 4.2
== 4.1
== 4.0.2
== 4.4.3
== 4.0.4
== 4.3
== 4.0.1
== 4.2.1
== 4.0.3
== 4.0
== 4.4
== 4.4.1
== 4.2.2
== 4.3.1
== 4.4.2
== 4.1.2
|
CVE-2016-3754
|
High
|
|
Jul 11, 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-3755
|
High
|
|
Jul 11, 2016
|
== 6.0.1
== 6.0
|
CVE-2016-3756
|
High
|
|
Jul 11, 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-3757
|
High
|
|
Jul 11, 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-3758
|
High
|
|
Jul 11, 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-3759
|
Low
|
|
Jul 11, 2016
|
== 5.1.0
== 6.0.1
== 6.0
== 5.0.1
== 5.0
== 5.1
|
CVE-2012-6702
|
Medium
|
|
Jun 16, 2016
|
== 4.4.4
== 5.0.2
== 5.1.1
== 6.0
== 6.0.1
|
CVE-2016-5300
|
High
|
|
Jun 16, 2016
|
== 4.4.4
== 5.0.2
== 5.1.1
== 6.0
== 6.0.1
|