Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-5597
|
High
|
|
Jan 25, 2017
|
== 2.0.0
== 2.0.4
== 2.2.0
== 2.0.9
== 2.2.2
== 2.0.1
== 2.2.1
== 2.0.7
== 2.0.2
== 2.0.8
== 2.0.3
== 2.0.6
== 2.2.3
== 2.0.5
|
CVE-2016-9372
|
Medium
|
|
Nov 17, 2016
|
== 2.2.0
== 2.2.1
|
CVE-2016-9373
|
Medium
|
|
Nov 17, 2016
|
== 2.0.0
== 2.0.4
== 2.2.0
== 2.0.1
== 2.2.1
== 2.0.7
== 2.0.2
== 2.0.3
== 2.0.6
== 2.0.5
|
CVE-2016-9374
|
Medium
|
|
Nov 17, 2016
|
== 2.0.0
== 2.0.4
== 2.2.0
== 2.0.1
== 2.2.1
== 2.0.7
== 2.0.2
== 2.0.3
== 2.0.6
== 2.0.5
|
CVE-2016-9375
|
Medium
|
|
Nov 17, 2016
|
== 2.0.0
== 2.0.4
== 2.2.0
== 2.0.1
== 2.2.1
== 2.0.7
== 2.0.2
== 2.0.3
== 2.0.6
== 2.0.5
|
CVE-2016-9376
|
Medium
|
|
Nov 17, 2016
|
== 2.0.0
== 2.0.4
== 2.2.0
== 2.0.1
== 2.2.1
== 2.0.7
== 2.0.2
== 2.0.3
== 2.0.6
== 2.0.5
|
CVE-2016-7175
|
Medium
|
|
Sep 9, 2016
|
== 2.0.0
== 2.0.4
== 2.0.1
== 2.0.2
== 2.0.3
== 2.0.5
|
CVE-2016-7176
|
Medium
|
|
Sep 9, 2016
|
== 2.0.0
== 2.0.1
== 2.0.2
== 2.0.3
== 2.0.4
== 2.0.5
|
CVE-2016-7177
|
Medium
|
|
Sep 9, 2016
|
== 2.0.0
== 2.0.1
== 2.0.2
== 2.0.3
== 2.0.4
== 2.0.5
|
CVE-2016-7178
|
Medium
|
|
Sep 9, 2016
|
== 2.0.0
== 2.0.1
== 2.0.2
== 2.0.3
== 2.0.4
== 2.0.5
|