Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2018-0711
|
Medium
|
|
Apr 30, 2018
|
== 4.3.4.0604
== 4.3.3.0570
== 4.3.4.0597
== 4.3.4.0593
== 4.3.3.0546
== 4.3.4.0569
== 4.3.4.0561
== 4.3.4.0516
== 4.3.3.0514
== 4.3.4.0526
== 4.3.4.0551
== 4.3.4.0557
|
CVE-2017-7630
|
Medium
|
|
Mar 27, 2018
|
== 4.3.3
== 4.2.6
|
CVE-2017-7631
|
Medium
|
|
Mar 27, 2018
|
== 4.3.3
== 4.2.6
|
CVE-2017-7632
|
Medium
|
|
Mar 27, 2018
|
== 4.3.3
== 4.2.6
|
CVE-2017-17027
|
Critical
|
|
Dec 21, 2017
|
== 4.3.4.0387-beta2
<= 4.3.3.0378
== 4.3.4.0370-beta1
== 4.3.4.0372-beta1
== 4.3.4.0374-beta1
== 4.3.4.0358-beta1
|
CVE-2017-17028
|
Critical
|
|
Dec 21, 2017
|
== 4.3.4.0387-beta2
<= 4.3.3.0378
== 4.3.4.0370-beta1
== 4.3.4.0372-beta1
== 4.3.4.0374-beta1
== 4.3.4.0358-beta1
|
CVE-2017-17029
|
Critical
|
|
Dec 21, 2017
|
== 4.3.4.0387-beta2
<= 4.3.3.0378
== 4.3.4.0370-beta1
== 4.3.4.0372-beta1
== 4.3.4.0374-beta1
== 4.3.4.0358-beta1
|
CVE-2017-17030
|
Critical
|
|
Dec 21, 2017
|
== 4.3.4.0387-beta2
<= 4.3.3.0378
== 4.3.4.0370-beta1
== 4.3.4.0372-beta1
== 4.3.4.0374-beta1
== 4.3.4.0358-beta1
|
CVE-2017-17031
|
Critical
|
|
Dec 21, 2017
|
== 4.3.4.0387-beta2
<= 4.3.3.0378
== 4.3.4.0370-beta1
== 4.3.4.0372-beta1
== 4.3.4.0374-beta1
== 4.3.4.0358-beta1
|
CVE-2017-17032
|
Critical
|
|
Dec 21, 2017
|
== 4.3.4.0387-beta2
<= 4.3.3.0378
== 4.3.4.0370-beta1
== 4.3.4.0372-beta1
== 4.3.4.0374-beta1
== 4.3.4.0358-beta1
|