Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-4866
|
Low
|
|
Apr 17, 2017
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 10.4.0
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|
CVE-2016-4867
|
Low
|
|
Apr 17, 2017
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 10.4.0
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|
CVE-2016-4868
|
Low
|
|
Apr 17, 2017
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 10.4.0
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|
CVE-2016-4869
|
Medium
|
|
Apr 17, 2017
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 10.4.0
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|
CVE-2016-4870
|
Medium
|
|
Apr 17, 2017
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 10.4.0
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|
CVE-2016-4871
|
Medium
|
|
Apr 17, 2017
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 10.4.0
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|
CVE-2016-4872
|
Low
|
|
Apr 17, 2017
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 10.4.0
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|
CVE-2016-4873
|
Low
|
|
Apr 17, 2017
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 10.4.0
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|
CVE-2016-4874
|
Low
|
|
Apr 17, 2017
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 10.4.0
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|
CVE-2015-7795
|
Medium
|
|
Feb 17, 2016
|
== 10.0.0
== 9.3.0
== 9.2.1
== 10.3.0
== 9.9.0
== 10.1.2
== 10.1.0
== 10.0.2
== 10.0.1
== 9.3.1
== 9.3.2
== 9.1.0
== 9.2.0
== 9.0
== 10.2.0
|