| Title |
Severity |
Exploit |
Date |
Affected Version |
|
CVE-2017-18909
|
High
|
|
Jun 19, 2020
|
< 3.9.0
|
|
CVE-2017-18910
|
Low
|
|
Jun 19, 2020
|
>= 3.7.0 < 3.7.5
>= 3.8.0 < 3.8.2
< 3.6.7
|
|
CVE-2017-18911
|
Critical
|
|
Jun 19, 2020
|
>= 3.7.0 < 3.7.5
>= 3.8.0 < 3.8.2
< 3.6.7
|
|
CVE-2017-18912
|
Critical
|
|
Jun 19, 2020
|
>= 3.7.0 < 3.7.5
>= 3.8.0 < 3.8.2
< 3.6.7
|
|
CVE-2017-18878
|
Low
|
|
Jun 19, 2020
|
>= 4.2.0 < 4.2.1
== 4.3.0-rc2
== 4.3.0-rc3
== 4.3.0-rc4
== 4.3.0-rc1
< 4.1.2
|
|
CVE-2017-18879
|
Medium
|
|
Jun 19, 2020
|
>= 4.2.0 < 4.2.1
== 4.3.0-rc2
== 4.3.0-rc3
== 4.3.0-rc4
== 4.3.0-rc1
< 4.1.2
|
|
CVE-2017-18880
|
Medium
|
|
Jun 19, 2020
|
>= 4.2.0 < 4.2.1
== 4.3.0-rc2
== 4.3.0-rc3
== 4.3.0-rc4
== 4.3.0-rc1
< 4.1.2
|
|
CVE-2017-18881
|
Medium
|
|
Jun 19, 2020
|
>= 4.2.0 < 4.2.1
== 4.3.0-rc2
== 4.3.0-rc3
== 4.3.0-rc4
== 4.3.0-rc1
< 4.1.2
|
|
CVE-2017-18882
|
Medium
|
|
Jun 19, 2020
|
>= 4.2.0 < 4.2.1
== 4.3.0-rc2
== 4.3.0-rc3
== 4.3.0-rc4
== 4.3.0-rc1
< 4.1.2
|
|
CVE-2017-18883
|
Critical
|
|
Jun 19, 2020
|
>= 4.2.0 < 4.2.1
== 4.3.0-rc2
== 4.3.0-rc3
== 4.3.0-rc4
== 4.3.0-rc1
< 4.1.2
|