| Title |
Severity |
Exploit |
Date |
Affected Version |
|
CVE-2016-4122
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4123
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4124
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4125
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4127
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4128
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4129
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4130
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4131
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4132
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|