Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-2799
|
High
|
|
Mar 13, 2016
|
== 38.0
== 38.2.1
== 38.1.0
== 38.2.0
== 38.6.1
== 38.4.0
== 38.3.0
== 38.5.1
== 38.0.5
== 38.0.1
== 38.5.0
== 38.6.0
== 38.1.1
|
CVE-2016-2800
|
High
|
|
Mar 13, 2016
|
== 38.0
== 38.2.1
== 38.1.0
== 38.2.0
== 38.6.1
== 38.4.0
== 38.3.0
== 38.5.1
== 38.0.5
== 38.0.1
== 38.5.0
== 38.6.0
== 38.1.1
|
CVE-2016-2801
|
High
|
|
Mar 13, 2016
|
== 38.0
== 38.2.1
== 38.1.0
== 38.2.0
== 38.6.1
== 38.4.0
== 38.3.0
== 38.5.1
== 38.0.5
== 38.0.1
== 38.5.0
== 38.6.0
== 38.1.1
|
CVE-2016-2802
|
High
|
|
Mar 13, 2016
|
== 38.0
== 38.2.1
== 38.1.0
== 38.2.0
== 38.6.1
== 38.4.0
== 38.3.0
== 38.5.1
== 38.0.5
== 38.0.1
== 38.5.0
== 38.6.0
== 38.1.1
|
CVE-2016-1521
|
High
|
|
Feb 13, 2016
|
== 38.2.1
== 38.1.0
== 38.2.0
== 38.4.0
== 38.5.2
== 38.3.0
== 38.5.1
== 38.0.5
== 38.0.1
== 38.5.0
== 38.6.0
== 38.1.1
|
CVE-2016-1522
|
High
|
|
Feb 13, 2016
|
== 38.0
== 38.2.1
== 38.1.0
== 38.2.0
== 38.4.0
== 38.5.2
== 38.3.0
== 38.5.1
== 38.0.5
== 38.0.1
== 38.5.0
== 38.6.0
== 38.1.1
|
CVE-2016-1523
|
Medium
|
|
Feb 13, 2016
|
== 38.0
== 38.2.1
== 38.1.0
== 38.2.0
== 38.4.0
== 38.5.2
== 38.3.0
== 38.5.1
== 38.0.5
== 38.0.1
== 38.5.0
== 38.6.0
== 38.1.1
|
CVE-2016-1526
|
High
|
|
Feb 13, 2016
|
== 38.0
== 38.2.1
== 38.1.0
== 38.2.0
== 38.4.0
== 38.5.2
== 38.3.0
== 38.5.1
== 38.0.5
== 38.0.1
== 38.5.0
== 38.6.0
== 38.1.1
|
CVE-2016-1930
|
Critical
|
|
Jan 31, 2016
|
== 38.0
== 38.1.0
== 38.2.0
== 38.4.0
== 38.3.0
== 38.5.0
|
CVE-2016-1935
|
High
|
|
Jan 31, 2016
|
== 38.0
== 38.1.0
== 38.2.0
== 38.4.0
== 38.3.0
== 38.5.0
|