| Title |
Severity |
Exploit |
Date |
Affected Version |
|
CVE-2016-3416
|
Medium
|
|
Apr 21, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
== 12.1.2.0.0
|
|
CVE-2016-0638
|
Critical
|
|
Apr 21, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
== 12.1.2.0.0
|
|
CVE-2016-0675
|
Medium
|
|
Apr 21, 2016
|
== 12.1.3.0.0
== 10.3.6.0.0
== 12.1.2.0.0
|
|
CVE-2016-0688
|
Low
|
|
Apr 21, 2016
|
== 12.1.3.0.0
== 10.3.6.0.0
== 12.1.2.0.0
|
|
CVE-2016-0696
|
Medium
|
|
Apr 21, 2016
|
== 10.3.6.0.0
|
|
CVE-2016-0700
|
Medium
|
|
Apr 21, 2016
|
== 12.1.3.0.0
== 10.3.6.0.0
== 12.1.2.0.0
|
|
CVE-2016-0572
|
High
|
|
Jan 21, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
== 12.1.2.0.0
|
|
CVE-2016-0573
|
High
|
|
Jan 21, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
== 12.1.2.0.0
|
|
CVE-2016-0574
|
High
|
|
Jan 21, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
== 12.1.2.0.0
|
|
CVE-2016-0577
|
High
|
|
Jan 21, 2016
|
== 12.2.1.0.0
== 12.1.3.0.0
== 10.3.6.0.0
== 12.1.2.0.0
|