Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-2836
|
High
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-2837
|
Medium
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-2838
|
High
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-2839
|
Medium
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5252
|
High
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5254
|
Critical
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5258
|
High
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5259
|
High
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5262
|
Medium
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5263
|
High
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|