Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-6131
|
Critical
|
|
May 23, 2017
|
== 13.0.0
== 12.1.1
== 12.1.2
== 12.0.0
== 12.1.0
|
CVE-2016-7476
|
High
|
|
May 11, 2017
|
== 11.5.2
== 11.5.0
== 11.4.0
== 11.5.3
== 11.4.1
== 11.3.0
== 11.6.0
== 11.5.1
|
CVE-2016-9250
|
High
|
|
May 10, 2017
|
== 12.1.1
== 12.1.2
== 11.5.2
== 11.5.0
== 12.0.0
== 11.4.0
== 11.5.3
== 11.6.1
== 11.4.1
== 11.5.4
== 12.1.0
== 11.6.0
== 11.5.1
|
CVE-2016-9251
|
High
|
|
May 9, 2017
|
== 12.0.0
== 12.1.0
== 12.1.1
== 12.1.2
|
CVE-2016-9253
|
High
|
|
May 9, 2017
|
== 12.1.0
== 12.1.1
== 12.1.2
|
CVE-2016-9256
|
High
|
|
May 9, 2017
|
== 12.0.0
== 12.1.0
== 12.1.1
== 12.1.2
|
CVE-2017-6137
|
Medium
|
|
May 9, 2017
|
== 12.1.1
== 12.1.2
== 12.0.0
== 11.6.1
== 12.1.0
|
CVE-2017-6128
|
High
|
|
May 1, 2017
|
== 11.5.2
== 11.5.0
== 11.4.0
== 11.5.3
== 11.6.1
== 11.4.1
== 11.5.4
== 11.6.0
== 11.5.1
|
CVE-2016-9252
|
High
|
|
Mar 27, 2017
|
== 12.1.1
== 11.5.2
== 11.5.0
== 12.0.0
== 11.4.0
== 11.5.3
== 11.6.1
== 11.4.1
== 11.5.4
== 12.1.0
== 11.6.0
== 11.5.1
|
CVE-2016-7474
|
Medium
|
|
Mar 27, 2017
|
== 12.1.1
== 11.5.2
== 11.5.0
== 12.0.0
== 11.4.0
== 11.5.3
== 11.6.1
== 11.4.1
== 11.5.4
== 12.1.0
== 11.6.0
== 11.5.1
|