| Title |
Severity |
Exploit |
Date |
Affected Version |
|
CVE-2017-3531
|
High
|
|
Apr 24, 2017
|
== 12.2.1.0.0
== 12.1.3.0.0
== 12.2.1.2.0
== 12.2.1.1.0
|
|
CVE-2017-5645
|
Critical
|
|
Apr 17, 2017
|
== 12.1.3.0.0
== 10.3.6.0.0
== 12.2.1.3.0
== 12.2.1.4.0
== 14.1.1.0.0
|
|
CVE-2016-7103
|
Medium
|
|
Mar 15, 2017
|
== 12.1.3.0.0
== 10.3.6.0.0
== 12.2.1.3.0
|
|
CVE-2017-5638
|
Critical
|
|
Mar 11, 2017
|
== 12.1.3.0.0
== 12.2.1.2.0
== 10.3.6.0.0
== 12.2.1.1.0
|
|
CVE-2017-3248
|
Critical
|
|
Jan 27, 2017
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
== 12.2.1.1.0
|
|
CVE-2016-5601
|
Medium
|
|
Oct 25, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 12.2.1.1.0
|
|
CVE-2016-5531
|
Critical
|
|
Oct 25, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
|
|
CVE-2016-5535
|
Critical
|
|
Oct 25, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
== 12.2.1.1.0
|
|
CVE-2016-3505
|
High
|
|
Oct 25, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
|
|
CVE-2016-3551
|
Critical
|
|
Oct 25, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 11.1.1.9.0
== 11.1.1.7.0
|