Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-4153
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
CVE-2016-4154
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
CVE-2016-4155
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
CVE-2016-4156
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
CVE-2016-4160
|
Critical
|
|
Jun 16, 2016
|
<= 11.2.202.616
<= 18.0.0.343
<= 21.0.0.216
<= 21.0.0.241
|
CVE-2016-4161
|
Critical
|
|
Jun 16, 2016
|
<= 11.2.202.616
<= 18.0.0.343
<= 21.0.0.216
<= 21.0.0.241
|
CVE-2016-4162
|
Critical
|
|
Jun 16, 2016
|
<= 11.2.202.616
<= 18.0.0.343
<= 21.0.0.216
<= 21.0.0.241
|
CVE-2016-4163
|
Critical
|
|
Jun 16, 2016
|
<= 11.2.202.616
<= 18.0.0.343
<= 21.0.0.216
<= 21.0.0.241
|
CVE-2016-4166
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
CVE-2016-4171
|
Critical
|
|
Jun 16, 2016
|
<= 18.0.0.352
<= 21.0.0.242
|