| Title |
Severity |
Exploit |
Date |
Affected Version |
|
CVE-2017-9788
|
Critical
|
|
Jul 13, 2017
|
<= 2.2.33
>= 2.4.0 <= 2.4.26
|
|
CVE-2017-9789
|
High
|
|
Jul 13, 2017
|
== 2.4.26
|
|
CVE-2017-3167
|
Critical
|
|
Jun 20, 2017
|
>= 2.2.0 < 2.2.33
>= 2.4.0 < 2.4.26
|
|
CVE-2017-3169
|
Critical
|
|
Jun 20, 2017
|
== 2.2.23
== 2.4.1
== 2.4.20
== 2.2.11
== 2.2.0
== 2.2.31
== 2.2.13
== 2.2.2
== 2.4.12
== 2.2.17
== 2.2.16
== 2.2.21
== 2.4.23
== 2.4.10
== 2.2.14
== 2.2.24
== 2.2.25
== 2.2.30
== 2.2.22
== 2.2.19
== 2.2.27
== 2.4.25
== 2.4.18
== 2.2.18
== 2.2.12
== 2.2.32
== 2.2.29
== 2.2.3
== 2.4.2
== 2.2.15
== 2.2.20
== 2.4.17
== 2.4.16
== 2.2.26
|
|
CVE-2017-7668
|
High
|
|
Jun 20, 2017
|
== 2.2.32
== 2.4.24
== 2.4.25
|
|
CVE-2017-7679
|
Critical
|
|
Jun 20, 2017
|
>= 2.2.0 < 2.2.33
>= 2.4.0 < 2.4.26
|
|
CVE-2016-8740
|
High
|
|
Dec 5, 2016
|
== 2.4.20
== 2.4.23
== 2.4.18
== 2.4.22
== 2.4.19
== 2.4.17
== 2.4.21
|
|
CVE-2016-5387
|
High
|
|
Jul 19, 2016
|
>= 2.2.0 <= 2.2.31
>= 2.4.1 <= 2.4.23
|
|
CVE-2016-1546
|
Medium
|
|
Jul 6, 2016
|
== 2.4.18
== 2.4.17
|
|
CVE-2016-4979
|
High
|
|
Jul 6, 2016
|
== 2.4.20
== 2.4.18
== 2.4.19
|