This page was not yet optimized for use on mobile devices.
Adobe Flash Player 23.0.0.205 for Edge
Configuration details
| CPE title | Adobe Flash Player 23.0.0.205 for Edge |
|---|---|
| URI | cpe:2.3:a:adobe:flash_player:23.0.0.205:*:*:*:*:edge:*:* |
Linked CVEs
143 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-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-2016-7867 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7868 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7869 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7870 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7871 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7872 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7873 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7874 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7875 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7876 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7877 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7878 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7879 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7880 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7881 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7890 | HIGH | 8.8 | 15.12.2016 | |
| CVE-2016-7892 | HIGH | 8.8 | 15.12.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-11292 | HIGH | 8.8 | 22.10.2017 | |
| CVE-2017-11305 | MEDIUM | 6.5 | 13.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-2982 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2984 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2985 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2986 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2987 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2988 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2990 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2991 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2992 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2993 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2994 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2995 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2996 | HIGH | 8.8 | 15.02.2017 | |
| CVE-2017-2997 | HIGH | 8.8 | 14.03.2017 | |
| CVE-2017-2998 | HIGH | 8.8 | 14.03.2017 | |
| CVE-2017-2999 | HIGH | 8.8 | 14.03.2017 | |
| CVE-2017-3000 | MEDIUM | 6.5 | 14.03.2017 | |
| CVE-2017-3001 | HIGH | 8.8 | 14.03.2017 | |
| CVE-2017-3002 | HIGH | 8.8 | 14.03.2017 | |
| CVE-2017-3003 | HIGH | 8.8 | 14.03.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-3068 | HIGH | 8.8 | 09.05.2017 | |
| CVE-2017-3069 | HIGH | 8.8 | 09.05.2017 | |
| CVE-2017-3070 | HIGH | 8.8 | 09.05.2017 | |
| CVE-2017-3071 | HIGH | 8.8 | 09.05.2017 | |
| CVE-2017-3072 | HIGH | 8.8 | 09.05.2017 | |
| CVE-2017-3073 | HIGH | 8.8 | 09.05.2017 | |
| CVE-2017-3074 | HIGH | 8.8 | 09.05.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-3080 | MEDIUM | 6.5 | 17.07.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-3085 | HIGH | 7.4 | 11.08.2017 | |
| CVE-2017-3099 | HIGH | 8.8 | 17.07.2017 | |
| CVE-2017-3100 | MEDIUM | 6.5 | 17.07.2017 | |
| CVE-2017-3106 | HIGH | 8.8 | 11.08.2017 | |
| CVE-2017-3112 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2017-3114 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2018-12824 | MEDIUM | 5.9 | 29.08.2018 | |
| 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-15967 | HIGH | 7.5 | 25.09.2018 | |
| CVE-2018-15978 | HIGH | 7.5 | 29.11.2018 | |
| CVE-2018-15981 | CRITICAL | 9.8 | 29.11.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-4919 | HIGH | 8.8 | 19.05.2018 | |
| CVE-2018-4920 | HIGH | 8.8 | 19.05.2018 | |
| CVE-2018-4932 | HIGH | 8.8 | 19.05.2018 | |
| CVE-2018-4933 | MEDIUM | 6.5 | 19.05.2018 | |
| CVE-2018-4934 | MEDIUM | 6.5 | 19.05.2018 | |
| CVE-2018-4935 | HIGH | 8.8 | 19.05.2018 | |
| CVE-2018-4936 | MEDIUM | 6.5 | 19.05.2018 | |
| CVE-2018-4937 | HIGH | 8.8 | 19.05.2018 | |
| CVE-2018-4944 | CRITICAL | 9.8 | 19.05.2018 | |
| CVE-2018-4945 | HIGH | 8.8 | 09.07.2018 | |
| CVE-2018-5000 | MEDIUM | 6.5 | 09.07.2018 | |
| CVE-2018-5001 | MEDIUM | 6.5 | 09.07.2018 | |
| CVE-2018-5002 | HIGH | 7.8 | 09.07.2018 | |
| CVE-2018-5007 | HIGH | 8.8 | 20.07.2018 | |
| CVE-2018-5008 | HIGH | 7.5 | 20.07.2018 | |
| CVE-2019-7090 | MEDIUM | 6.5 | 24.05.2019 | |
| CVE-2019-7096 | CRITICAL | 9.8 | 23.05.2019 | |
| CVE-2019-7108 | HIGH | 7.5 | 23.05.2019 | |
| CVE-2019-7837 | HIGH | 8.8 | 22.05.2019 | |
| CVE-2019-7845 | HIGH | 8.8 | 12.06.2019 | |
| CVE-2019-8069 | CRITICAL | 9.8 | 12.09.2019 | |
| CVE-2019-8070 | CRITICAL | 9.8 | 12.09.2019 | |
| CVE-2019-8075 | HIGH | 7.5 | 27.09.2019 | |
| CVE-2020-3757 | HIGH | 8.8 | 13.02.2020 | |
| CVE-2020-9633 | CRITICAL | 9.8 | 12.06.2020 | |
| CVE-2020-9746 | HIGH | 8.8 | 14.10.2020 |
Showing 5 out of 143.
Matched certificates
This CPE has no matched certificates.