| Title |
Severity |
Exploit |
Date |
Affected Version |
|
CVE-2016-4133
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4134
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4135
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4136
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4137
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4138
|
Critical
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4139
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4140
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4141
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|
|
CVE-2016-4142
|
High
|
|
Jun 16, 2016
|
<= 11.2.202.621
<= 18.0.0.352
<= 21.0.0.242
|