Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-9351
|
High
|
|
Jun 2, 2017
|
>= 2.0.0 <= 2.0.12
>= 2.2.0 <= 2.2.6
|
CVE-2017-9352
|
High
|
|
Jun 2, 2017
|
>= 2.0.0 <= 2.0.12
>= 2.2.0 <= 2.2.6
|
CVE-2017-9353
|
High
|
|
Jun 2, 2017
|
>= 2.2.0 <= 2.2.6
|
CVE-2017-9354
|
High
|
|
Jun 2, 2017
|
>= 2.0.0 <= 2.0.12
>= 2.2.0 <= 2.2.6
|
CVE-2017-7700
|
Medium
|
|
Apr 13, 2017
|
>= 2.0.0 <= 2.0.11
>= 2.2.0 <= 2.2.5
|
CVE-2017-7701
|
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-7702
|
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-7703
|
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-7704
|
High
|
|
Apr 13, 2017
|
== 2.2.0
== 2.2.2
== 2.2.1
== 2.2.4
== 2.2.5
== 2.2.3
|
CVE-2017-7705
|
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
|