Title |
Severity |
Exploit |
Date |
Affected Version |
CVE-2016-1977
|
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-2790
|
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-2791
|
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-2792
|
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-2793
|
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-2794
|
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-2795
|
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-2796
|
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-2797
|
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-2798
|
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
|