Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-6471
|
High
|
|
Mar 4, 2017
|
>= 2.0.0 <= 2.0.10
>= 2.2.0 <= 2.2.4
|
CVE-2017-6472
|
High
|
|
Mar 4, 2017
|
>= 2.0.0 <= 2.0.10
>= 2.2.0 <= 2.2.4
|
CVE-2017-6473
|
High
|
|
Mar 4, 2017
|
>= 2.0.0 <= 2.0.10
>= 2.2.0 <= 2.2.4
|
CVE-2017-6474
|
High
|
|
Mar 4, 2017
|
>= 2.0.0 <= 2.0.10
>= 2.2.0 <= 2.2.4
|
CVE-2017-6014
|
High
|
|
Feb 17, 2017
|
<= 2.2.4
|
CVE-2017-5596
|
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-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
|