Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-3809
|
Medium
|
|
Feb 3, 2017
|
== 6.1.0
== 6.2.0
|
CVE-2017-3814
|
Medium
|
|
Feb 3, 2017
|
== 5.3.0
== 6.0.1
== 6.0.0
== 6.1.0
== 5.4.0
|
CVE-2016-9193
|
High
|
|
Dec 14, 2016
|
== 6.0.0.0
== 6.0.1.1
== 6.0.1
== 6.0.0
== 6.1.0
== 6.0.0.1
|
CVE-2016-6439
|
High
|
|
Oct 27, 2016
|
== 6.0.0.0
== 5.3.0
== 5.3.0.4
== 5.3.1.5
== 5.3.1.4
== 5.3.0.3
== 5.4.1.6
== 5.4.1.1
== 6.0.1
== 5.4.1
== 5.3.0.2
== 6.0.0
== 5.4_base
== 5.4.1.3
== 5.3.1
== 6.0_base
== 5.3.1.3
== 5.4.1.5
== 6.0.0.1
== 5.4.0
== 5.4.1.2
== 5.3.1.6
== 5.4.1.4
== 5.4.0.2
|
CVE-2016-6433
|
High
|
|
Oct 6, 2016
|
== 5.2.0
== 5.3.0
== 5.3.0.2
== 5.3.0.3
== 5.3.0.4
== 5.3.1
== 5.3.1.3
== 5.3.1.4
== 5.3.1.5
== 5.3.1.6
== 5.4.0
== 5.4.0.2
== 5.4.1
== 5.4.1.1
== 5.4.1.2
== 5.4.1.3
== 5.4.1.4
== 5.4.1.5
== 5.4.1.6
== 6.0.1
|
CVE-2016-6434
|
High
|
|
Oct 6, 2016
|
== 6.0.1
|
CVE-2016-6435
|
Medium
|
|
Oct 6, 2016
|
== 6.0.1
|
CVE-2016-6419
|
High
|
|
Oct 5, 2016
|
== 5.3.0
== 5.3.1
== 5.4.0
== 4.10.3
== 5.2.0
|
CVE-2016-6365
|
Medium
|
|
Aug 23, 2016
|
== 5.3.0
== 5.3.0.2
== 5.3.1
== 5.4.0
== 4.10.3
== 5.2.0
|
CVE-2016-1457
|
High
|
|
Aug 18, 2016
|
== 5.3.0.4
== 4.10.3.9
== 5.3.1
== 5.4.0
== 5.2.0
|