Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-4103
|
Critical
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|
CVE-2016-4104
|
Critical
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|
CVE-2016-4105
|
Critical
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|
CVE-2016-4106
|
High
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|
CVE-2016-1037
|
Critical
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|
CVE-2016-1038
|
Critical
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|
CVE-2016-1039
|
Critical
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|
CVE-2016-1040
|
Critical
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|
CVE-2016-1041
|
Critical
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|
CVE-2016-1042
|
Critical
|
|
May 11, 2016
|
<= 15.006.30121
<= 15.010.20060
|