This page was not yet optimized for use on mobile devices.
Adobe Flash Player 18.0.0.343 Extended Support Release (ESR)
Configuration details
| CPE title | Adobe Flash Player 18.0.0.343 Extended Support Release (ESR) |
|---|---|
| URI | cpe:2.3:a:adobe:flash_player:18.0.0.343:*:*:*:esr:*:*:* |
Linked CVEs
238 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2005-4708 | HIGH | 7.2 | 31.12.2005 | |
| CVE-2008-1654 | MEDIUM | 4.3 | 02.04.2008 | |
| CVE-2008-3873 | MEDIUM | 4.3 | 29.08.2008 | |
| CVE-2010-0209 | HIGH | 9.3 | 11.08.2010 | |
| CVE-2010-2213 | HIGH | 9.3 | 11.08.2010 | |
| CVE-2010-2214 | HIGH | 9.3 | 11.08.2010 | |
| CVE-2010-2215 | MEDIUM | 4.3 | 11.08.2010 | |
| CVE-2010-2216 | HIGH | 9.3 | 11.08.2010 | |
| CVE-2015-5569 | HIGH | 10.0 | 14.10.2015 | |
| CVE-2015-7625 | HIGH | 10.0 | 14.10.2015 | |
| CVE-2015-7626 | HIGH | 10.0 | 14.10.2015 | |
| CVE-2015-7627 | HIGH | 10.0 | 15.10.2015 | |
| CVE-2015-7628 | MEDIUM | 5.0 | 15.10.2015 | |
| CVE-2015-7629 | HIGH | 9.3 | 15.10.2015 | |
| CVE-2015-7630 | HIGH | 10.0 | 15.10.2015 | |
| CVE-2015-7631 | HIGH | 9.3 | 15.10.2015 | |
| CVE-2015-7632 | HIGH | 9.3 | 15.10.2015 | |
| CVE-2015-7633 | HIGH | 10.0 | 15.10.2015 | |
| CVE-2015-7634 | HIGH | 10.0 | 15.10.2015 | |
| CVE-2015-7635 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2015-7636 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2015-7637 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2015-7638 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2015-7639 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2015-7640 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2015-7641 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2015-7642 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2015-7643 | HIGH | 9.3 | 15.10.2015 | |
| CVE-2015-7644 | HIGH | 10.0 | 15.10.2015 | |
| CVE-2015-7647 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2015-7648 | HIGH | 10.0 | 18.10.2015 | |
| CVE-2016-0959 | CRITICAL | 9.8 | 27.06.2017 | |
| CVE-2016-1096 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1097 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1098 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1099 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1100 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1101 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1102 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1103 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1104 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1105 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1106 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1107 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1108 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1109 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-1110 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4108 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4109 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4110 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4111 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4112 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4113 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4114 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4115 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4116 | HIGH | 7.5 | 11.05.2016 | |
| CVE-2016-4117 | CRITICAL | 9.8 | 11.05.2016 | |
| CVE-2016-4120 | CRITICAL | 9.8 | 16.06.2016 | |
| CVE-2016-4121 | CRITICAL | 9.8 | 16.06.2016 | |
| CVE-2016-4122 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4123 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4124 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4125 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4127 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4128 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4129 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4130 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4131 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4132 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4133 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4134 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4135 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4136 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4137 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4138 | CRITICAL | 9.8 | 16.06.2016 | |
| CVE-2016-4139 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4140 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4141 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4142 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4143 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4144 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4145 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4146 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4147 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4148 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4149 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4150 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4151 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4152 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4153 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4154 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4155 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4156 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4160 | CRITICAL | 9.8 | 16.06.2016 | |
| CVE-2016-4161 | CRITICAL | 9.8 | 16.06.2016 | |
| CVE-2016-4162 | CRITICAL | 9.8 | 16.06.2016 | |
| CVE-2016-4163 | CRITICAL | 9.8 | 16.06.2016 | |
| CVE-2016-4166 | HIGH | 8.8 | 16.06.2016 | |
| CVE-2016-4171 | CRITICAL | 9.8 | 16.06.2016 | |
| CVE-2016-4172 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4173 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4174 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4175 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4176 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4177 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4178 | MEDIUM | 4.3 | 13.07.2016 | |
| CVE-2016-4179 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4180 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4181 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4182 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4183 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4184 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4185 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4186 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4187 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4188 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4189 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4190 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4217 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4218 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4219 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4220 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4221 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4222 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4223 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4224 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4225 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4226 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4227 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4228 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4229 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4230 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4231 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4232 | HIGH | 7.5 | 13.07.2016 | |
| CVE-2016-4233 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4234 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4235 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4236 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4237 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4238 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4239 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4240 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4241 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4242 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4243 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4244 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4245 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4246 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4247 | MEDIUM | 5.3 | 13.07.2016 | |
| CVE-2016-4248 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4249 | HIGH | 8.8 | 13.07.2016 | |
| CVE-2016-4271 | MEDIUM | 6.5 | 14.09.2016 | |
| CVE-2016-4272 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4274 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4275 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4276 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4277 | MEDIUM | 6.5 | 14.09.2016 | |
| CVE-2016-4278 | MEDIUM | 6.5 | 14.09.2016 | |
| CVE-2016-4279 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4280 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4281 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4282 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4283 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4284 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4285 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-4286 | HIGH | 8.8 | 13.10.2016 | |
| CVE-2016-4287 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6921 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6922 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6923 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6924 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6925 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6926 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6927 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6929 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6930 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6931 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-6932 | HIGH | 8.8 | 14.09.2016 | |
| CVE-2016-7020 | HIGH | 8.8 | 05.10.2016 | |
| CVE-2016-7855 | HIGH | 8.8 | 01.11.2016 | |
| CVE-2016-7857 | HIGH | 8.8 | 08.11.2016 | |
| CVE-2016-7858 | HIGH | 8.8 | 08.11.2016 | |
| CVE-2016-7859 | HIGH | 8.8 | 08.11.2016 | |
| CVE-2016-7860 | HIGH | 8.8 | 08.11.2016 | |
| CVE-2016-7861 | HIGH | 8.8 | 08.11.2016 | |
| CVE-2016-7862 | HIGH | 8.8 | 08.11.2016 | |
| CVE-2016-7863 | HIGH | 8.8 | 08.11.2016 | |
| CVE-2016-7864 | HIGH | 8.8 | 08.11.2016 | |
| CVE-2016-7865 | HIGH | 8.8 | 08.11.2016 | |
| CVE-2017-11213 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2017-11215 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2017-11225 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2017-11281 | CRITICAL | 9.8 | 01.12.2017 | |
| CVE-2017-11282 | CRITICAL | 9.8 | 01.12.2017 | |
| CVE-2017-2925 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2926 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2927 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2928 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2930 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2931 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2932 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2933 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2934 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2935 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2936 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2937 | HIGH | 8.8 | 11.01.2017 | |
| CVE-2017-2938 | MEDIUM | 6.5 | 11.01.2017 | |
| CVE-2017-3058 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3059 | CRITICAL | 9.8 | 12.04.2017 | |
| CVE-2017-3060 | CRITICAL | 9.8 | 12.04.2017 | |
| CVE-2017-3061 | CRITICAL | 9.8 | 12.04.2017 | |
| CVE-2017-3062 | CRITICAL | 9.8 | 12.04.2017 | |
| CVE-2017-3063 | CRITICAL | 9.8 | 12.04.2017 | |
| CVE-2017-3064 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3075 | CRITICAL | 9.8 | 20.06.2017 | |
| CVE-2017-3076 | CRITICAL | 9.8 | 20.06.2017 | |
| CVE-2017-3077 | CRITICAL | 9.8 | 20.06.2017 | |
| CVE-2017-3078 | CRITICAL | 9.8 | 20.06.2017 | |
| CVE-2017-3079 | CRITICAL | 9.8 | 20.06.2017 | |
| CVE-2017-3081 | CRITICAL | 9.8 | 20.06.2017 | |
| CVE-2017-3082 | CRITICAL | 9.8 | 20.06.2017 | |
| CVE-2017-3083 | CRITICAL | 9.8 | 20.06.2017 | |
| CVE-2017-3084 | CRITICAL | 9.8 | 20.06.2017 | |
| CVE-2017-3112 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2017-3114 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2018-12825 | CRITICAL | 9.8 | 29.08.2018 | |
| CVE-2018-12826 | HIGH | 7.5 | 29.08.2018 | |
| CVE-2018-12827 | HIGH | 7.5 | 29.08.2018 | |
| CVE-2018-12828 | CRITICAL | 9.8 | 29.08.2018 | |
| CVE-2018-15982 | HIGH | 7.8 | 18.01.2019 | |
| CVE-2018-15983 | HIGH | 7.8 | 18.01.2019 | |
| CVE-2018-4871 | HIGH | 7.5 | 09.01.2018 | |
| CVE-2018-4877 | CRITICAL | 9.8 | 06.02.2018 | |
| CVE-2018-4878 | HIGH | 7.8 | 06.02.2018 | |
| CVE-2018-4944 | CRITICAL | 9.8 | 19.05.2018 | |
| CVE-2019-7845 | HIGH | 8.8 | 12.06.2019 | |
| CVE-2020-3757 | HIGH | 8.8 | 13.02.2020 | |
| CVE-2020-9746 | HIGH | 8.8 | 14.10.2020 |
Showing 5 out of 238.
Matched certificates
This CPE has no matched certificates.