| Title |
Severity |
Exploit |
Date |
Affected Version |
|
CVE-2019-16508
|
High
|
|
Oct 1, 2019
|
>= r75 < r75.12105.b
< r74-11895.b
>= r76 < r76.12208.0.0
|
|
CVE-2016-5179
|
Critical
|
|
Mar 7, 2018
|
< 53.0.2785.144
|
|
CVE-2017-15397
|
High
|
|
Feb 8, 2018
|
< 62.0.3202.74
|
|
CVE-2017-15400
|
High
|
|
Feb 8, 2018
|
< 62.0.3202.74
|
|
CVE-2017-5084
|
Low
|
|
Oct 27, 2017
|
< 59.0.3071.92
|
|
CVE-2016-5169
|
High
|
|
Sep 25, 2016
|
<= 52.0.2743.116
|
|
CVE-2014-3188
|
High
|
|
Oct 8, 2014
|
<= 38.0.2125.77
|
|
CVE-2014-1706
|
High
|
|
Mar 16, 2014
|
== 33.0.1750.51
== 33.0.1750.5
<= 33.0.1750.149
== 33.0.1750.70
== 33.0.1750.29
== 33.0.1750.2
== 33.0.1750.124
== 33.0.1750.16
== 33.0.1750.58
== 33.0.1750.93
== 33.0.1750.112
|
|
CVE-2014-1707
|
High
|
|
Mar 16, 2014
|
== 33.0.1750.51
== 33.0.1750.5
<= 33.0.1750.149
== 33.0.1750.70
== 33.0.1750.29
== 33.0.1750.2
== 33.0.1750.124
== 33.0.1750.16
== 33.0.1750.58
== 33.0.1750.93
== 33.0.1750.112
|
|
CVE-2014-1708
|
High
|
|
Mar 16, 2014
|
== 33.0.1750.51
== 33.0.1750.5
<= 33.0.1750.149
== 33.0.1750.70
== 33.0.1750.29
== 33.0.1750.2
== 33.0.1750.124
== 33.0.1750.16
== 33.0.1750.58
== 33.0.1750.93
== 33.0.1750.112
|