Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2017-3535
|
Low
|
|
Apr 24, 2017
|
== 12.0.2
== 11.3.0
== 11.4.0
== 12.0.3
== 12.0.1
|
CVE-2016-8297
|
High
|
|
Jan 27, 2017
|
== 12.0.2
== 11.3.0
== 12.2.0
== 12.1.0
== 11.4.0
== 12.0.3
== 12.0.1
|
CVE-2016-8299
|
Medium
|
|
Jan 27, 2017
|
== 12.0.2
== 11.3.0
== 12.2.0
== 12.1.0
== 11.4.0
== 12.0.3
== 12.0.1
|
CVE-2016-8301
|
Low
|
|
Jan 27, 2017
|
== 12.0.2
== 11.3.0
== 12.2.0
== 12.1.0
== 11.4.0
== 12.0.3
== 12.0.1
|
CVE-2016-8302
|
Low
|
|
Jan 27, 2017
|
== 12.0.2
== 11.3.0
== 12.2.0
== 12.1.0
== 11.4.0
== 12.0.3
== 12.0.1
|
CVE-2016-8303
|
Medium
|
|
Jan 27, 2017
|
== 12.0.2
== 11.3.0
== 12.2.0
== 12.1.0
== 11.4.0
== 12.0.3
== 12.0.1
|
CVE-2016-8304
|
Medium
|
|
Jan 27, 2017
|
== 12.0.2
== 11.3.0
== 12.2.0
== 12.1.0
== 11.4.0
== 12.0.3
== 12.0.1
|
CVE-2016-8305
|
Low
|
|
Jan 27, 2017
|
== 12.0.2
== 11.3.0
== 12.2.0
== 12.1.0
== 11.4.0
== 12.0.3
== 12.0.1
|
CVE-2016-8307
|
Medium
|
|
Jan 27, 2017
|
== 12.0.2
== 11.3.0
== 12.2.0
== 12.1.0
== 11.4.0
== 12.0.3
== 12.0.1
|
CVE-2016-8310
|
High
|
|
Jan 27, 2017
|
== 12.0.2
== 11.3.0
== 12.2.0
== 12.1.0
== 11.4.0
== 12.0.3
== 12.0.1
|