Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-11269
|
High
|
|
Aug 11, 2017
|
>= 17.011.00000 <= 17.011.30066
|
CVE-2017-11270
|
High
|
|
Aug 11, 2017
|
>= 17.011.00000 <= 17.011.30066
|
CVE-2017-11271
|
High
|
|
Aug 11, 2017
|
>= 17.011.00000 <= 17.011.30066
|
CVE-2016-1111
|
High
|
|
Apr 30, 2016
|
<= 9.0
|
CVE-2016-1007
|
Critical
|
|
Mar 9, 2016
|
<= 11.0.14
|
CVE-2016-1008
|
High
|
|
Mar 9, 2016
|
<= 11.0.14
|
CVE-2016-1009
|
Critical
|
|
Mar 9, 2016
|
<= 11.0.14
|
CVE-2016-0931
|
High
|
|
Jan 14, 2016
|
<= 11.0.13
== 11.0.0
== 11.0.1
== 11.0.10
== 11.0.11
== 11.0.12
== 11.0.2
== 11.0.3
== 11.0.4
== 11.0.5
== 11.0.6
== 11.0.7
== 11.0.8
== 11.0.9
|
CVE-2016-0932
|
High
|
|
Jan 14, 2016
|
<= 11.0.13
== 11.0.0
== 11.0.1
== 11.0.10
== 11.0.11
== 11.0.12
== 11.0.2
== 11.0.3
== 11.0.4
== 11.0.5
== 11.0.6
== 11.0.7
== 11.0.8
== 11.0.9
|
CVE-2016-0933
|
Critical
|
|
Jan 14, 2016
|
<= 11.0.13
== 11.0.0
== 11.0.1
== 11.0.10
== 11.0.11
== 11.0.12
== 11.0.2
== 11.0.3
== 11.0.4
== 11.0.5
== 11.0.6
== 11.0.7
== 11.0.8
== 11.0.9
|