Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-7745
|
High
|
|
Apr 13, 2017
|
== 2.0.0
== 2.0.4
== 2.2.0
== 2.0.9
== 2.2.2
== 2.0.1
== 2.2.1
== 2.2.4
== 2.0.11
== 2.0.7
== 2.0.2
== 2.0.8
== 2.0.3
== 2.2.5
== 2.0.6
== 2.0.10
== 2.2.3
== 2.0.5
|
CVE-2017-7746
|
High
|
|
Apr 13, 2017
|
== 2.0.0
== 2.0.4
== 2.2.0
== 2.0.9
== 2.2.2
== 2.0.1
== 2.2.1
== 2.2.4
== 2.0.11
== 2.0.7
== 2.0.2
== 2.0.8
== 2.0.3
== 2.2.5
== 2.0.6
== 2.0.10
== 2.2.3
== 2.0.5
|
CVE-2017-7747
|
High
|
|
Apr 13, 2017
|
== 2.0.0
== 2.0.4
== 2.2.0
== 2.0.9
== 2.2.2
== 2.0.1
== 2.2.1
== 2.2.4
== 2.0.11
== 2.0.7
== 2.0.2
== 2.0.8
== 2.0.3
== 2.2.5
== 2.0.6
== 2.0.10
== 2.2.3
== 2.0.5
|
CVE-2017-7748
|
High
|
|
Apr 13, 2017
|
== 2.0.0
== 2.0.4
== 2.2.0
== 2.0.9
== 2.2.2
== 2.0.1
== 2.2.1
== 2.2.4
== 2.0.11
== 2.0.7
== 2.0.2
== 2.0.8
== 2.0.3
== 2.2.5
== 2.0.6
== 2.0.10
== 2.2.3
== 2.0.5
|
CVE-2016-7957
|
High
|
|
Apr 12, 2017
|
== 2.2.0
|
CVE-2016-7958
|
High
|
|
Apr 12, 2017
|
== 2.2.0
|
CVE-2017-6467
|
High
|
|
Mar 4, 2017
|
>= 2.0.0 <= 2.0.10
>= 2.2.0 <= 2.2.4
|
CVE-2017-6468
|
High
|
|
Mar 4, 2017
|
>= 2.0.0 <= 2.0.10
>= 2.2.0 <= 2.2.4
|
CVE-2017-6469
|
High
|
|
Mar 4, 2017
|
>= 2.0.0 <= 2.0.10
>= 2.2.0 <= 2.2.4
|
CVE-2017-6470
|
High
|
|
Mar 4, 2017
|
>= 2.0.0 <= 2.0.10
>= 2.2.0 <= 2.2.4
|