Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-5270
|
Critical
|
|
Sep 23, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5272
|
High
|
|
Sep 23, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5274
|
Critical
|
|
Sep 23, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5276
|
Critical
|
|
Sep 23, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5277
|
Critical
|
|
Sep 23, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5278
|
High
|
|
Sep 23, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5280
|
Critical
|
|
Sep 23, 2016
|
== 45.0
== 45.0.1
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5281
|
Critical
|
|
Sep 23, 2016
|
== 45.0
== 45.0.1
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-5284
|
High
|
|
Sep 23, 2016
|
== 45.0
== 45.0.1
== 45.1.1
== 45.2.0
== 45.3.0
|
CVE-2016-2830
|
Low
|
|
Aug 5, 2016
|
== 45.1.0
== 45.1.1
== 45.2.0
== 45.3.0
|