This page was not yet optimized for use on mobile devices.
Adobe Acrobat 8.0 Professional
Configuration details
| CPE title | Adobe Acrobat 8.0 Professional |
|---|---|
| URI | cpe:2.3:a:adobe:acrobat:8.0:-:pro:*:*:*:*:* |
Linked CVEs
342 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2007-5659 | HIGH | 7.8 | 12.02.2008 | |
| CVE-2007-5663 | HIGH | 9.3 | 12.02.2008 | |
| CVE-2007-5666 | MEDIUM | 6.2 | 12.02.2008 | |
| CVE-2008-0655 | HIGH | 8.8 | 07.02.2008 | |
| CVE-2008-0726 | HIGH | 9.3 | 12.02.2008 | |
| CVE-2008-2042 | HIGH | 9.3 | 08.05.2008 | |
| CVE-2008-2992 | HIGH | 7.8 | 04.11.2008 | |
| CVE-2009-0198 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-0509 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-0510 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-0511 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-0512 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-0658 | HIGH | 7.8 | 20.02.2009 | |
| CVE-2009-0888 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-0889 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-0928 | HIGH | 10.0 | 25.03.2009 | |
| CVE-2009-1492 | HIGH | 9.3 | 30.04.2009 | |
| CVE-2009-1855 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-1856 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-1857 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-1858 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-1859 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-1861 | HIGH | 9.3 | 11.06.2009 | |
| CVE-2009-2028 | HIGH | 10.0 | 11.06.2009 | |
| CVE-2009-2979 | MEDIUM | 4.3 | 19.10.2009 | |
| CVE-2009-2980 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2981 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2982 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2983 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2984 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2985 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2986 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2987 | MEDIUM | 4.3 | 19.10.2009 | |
| CVE-2009-2988 | MEDIUM | 4.3 | 19.10.2009 | |
| CVE-2009-2989 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2990 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2991 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2992 | MEDIUM | 4.3 | 19.10.2009 | |
| CVE-2009-2993 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2994 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2995 | MEDIUM | 4.3 | 19.10.2009 | |
| CVE-2009-2996 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2997 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-2998 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-3431 | MEDIUM | 5.0 | 25.09.2009 | |
| CVE-2009-3458 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-3459 | HIGH | 9.3 | 13.10.2009 | |
| CVE-2009-3460 | HIGH | 9.3 | 19.10.2009 | |
| CVE-2009-3462 | MEDIUM | 5.1 | 19.10.2009 | |
| CVE-2009-3953 | HIGH | 8.8 | 13.01.2010 | |
| CVE-2009-3954 | HIGH | 10.0 | 13.01.2010 | |
| CVE-2009-3955 | HIGH | 10.0 | 13.01.2010 | |
| CVE-2009-3956 | HIGH | 10.0 | 13.01.2010 | |
| CVE-2009-3957 | MEDIUM | 5.0 | 13.01.2010 | |
| CVE-2009-3958 | HIGH | 10.0 | 13.01.2010 | |
| CVE-2009-3959 | HIGH | 10.0 | 13.01.2010 | |
| CVE-2009-4324 | HIGH | 7.8 | 15.12.2009 | |
| CVE-2010-0186 | MEDIUM | 6.8 | 15.02.2010 | |
| CVE-2010-0188 | HIGH | 7.8 | 22.02.2010 | |
| CVE-2010-0190 | MEDIUM | 4.3 | 14.04.2010 | |
| CVE-2010-0191 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0192 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0193 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0194 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0195 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0196 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0197 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0198 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0199 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0201 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0202 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0203 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-0204 | HIGH | 9.3 | 14.04.2010 | |
| CVE-2010-1278 | HIGH | 9.3 | 22.04.2010 | |
| CVE-2010-1285 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-1295 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-1297 | HIGH | 7.8 | 08.06.2010 | |
| CVE-2010-2168 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2201 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2202 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2204 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2205 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2206 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2207 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2208 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2209 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2210 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2211 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2212 | HIGH | 9.3 | 30.06.2010 | |
| CVE-2010-2883 | HIGH | 7.3 | 09.09.2010 | |
| CVE-2010-2884 | HIGH | 9.3 | 15.09.2010 | |
| CVE-2010-2888 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-2889 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-2890 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3619 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3620 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3621 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3622 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3623 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3624 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3625 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3626 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3627 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3628 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3629 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3630 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3631 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3632 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-3656 | MEDIUM | 4.3 | 06.10.2010 | |
| CVE-2010-3657 | MEDIUM | 4.3 | 06.10.2010 | |
| CVE-2010-3658 | HIGH | 9.3 | 06.10.2010 | |
| CVE-2010-4091 | HIGH | 9.3 | 07.11.2010 | |
| CVE-2011-0562 | MEDIUM | 6.9 | 10.02.2011 | |
| CVE-2011-0563 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0564 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0565 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0566 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0567 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0568 | MEDIUM | 6.8 | 10.02.2011 | |
| CVE-2011-0570 | MEDIUM | 6.9 | 10.02.2011 | |
| CVE-2011-0585 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0586 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0587 | MEDIUM | 4.3 | 10.02.2011 | |
| CVE-2011-0588 | MEDIUM | 6.9 | 10.02.2011 | |
| CVE-2011-0589 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0590 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0591 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0592 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0593 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0594 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0595 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0596 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0598 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0599 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0600 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0602 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0603 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-0604 | MEDIUM | 4.3 | 10.02.2011 | |
| CVE-2011-0605 | MEDIUM | 6.8 | 10.02.2011 | |
| CVE-2011-0606 | HIGH | 9.3 | 10.02.2011 | |
| CVE-2011-2094 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2095 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2096 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2097 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2098 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2099 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2100 | MEDIUM | 6.9 | 16.06.2011 | |
| CVE-2011-2101 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2103 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2104 | MEDIUM | 4.3 | 16.06.2011 | |
| CVE-2011-2105 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2106 | HIGH | 9.3 | 16.06.2011 | |
| CVE-2011-2107 | MEDIUM | 4.3 | 09.06.2011 | |
| CVE-2011-2431 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2432 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2433 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2434 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2435 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2436 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2437 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2438 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2439 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2440 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2441 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2442 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2462 | CRITICAL | 9.8 | 07.12.2011 | |
| CVE-2011-4370 | HIGH | 7.5 | 10.01.2012 | |
| CVE-2011-4371 | HIGH | 7.5 | 10.01.2012 | |
| CVE-2011-4372 | CRITICAL | 9.8 | 10.01.2012 | |
| CVE-2011-4373 | CRITICAL | 9.8 | 10.01.2012 | |
| CVE-2011-4374 | HIGH | 9.3 | 19.01.2012 | |
| CVE-2014-5315 | MEDIUM | 4.3 | 26.09.2014 | |
| CVE-2014-9150 | MEDIUM | 6.4 | 30.11.2014 | |
| CVE-2016-0931 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0932 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0933 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0934 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0935 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0936 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0937 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0938 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0939 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0940 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0941 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0942 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0943 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0944 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0945 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0946 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0947 | HIGH | 7.8 | 14.01.2016 | |
| CVE-2016-1007 | CRITICAL | 9.8 | 09.03.2016 | |
| CVE-2016-1008 | HIGH | 8.4 | 09.03.2016 | |
| CVE-2016-1009 | CRITICAL | 9.8 | 09.03.2016 | |
| CVE-2016-1111 | HIGH | 8.8 | 30.04.2016 | |
| CVE-2016-4095 | CRITICAL | 9.8 | 10.11.2016 | |
| CVE-2017-11293 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2017-16360 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16361 | MEDIUM | 6.5 | 09.12.2017 | |
| CVE-2017-16362 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16363 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16364 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16365 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16366 | HIGH | 7.5 | 09.12.2017 | |
| CVE-2017-16367 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16368 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16369 | MEDIUM | 6.5 | 09.12.2017 | |
| CVE-2017-16370 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16371 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16372 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16373 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16374 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16375 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16376 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16377 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16378 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16379 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16380 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16381 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16382 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16383 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16384 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16385 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16386 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16387 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16388 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16389 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16390 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16391 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16392 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16393 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16394 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16395 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16396 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16397 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16398 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2017-16399 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16400 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16401 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16402 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16403 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16404 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16405 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16406 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16407 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16408 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16409 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16410 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16411 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16412 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16413 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16414 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16415 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16416 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16417 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16418 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16419 | MEDIUM | 6.5 | 09.12.2017 | |
| CVE-2017-16420 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-2939 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2940 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2941 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2942 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2943 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2944 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2945 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2946 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2947 | MEDIUM | 5.5 | 11.01.2017 | |
| CVE-2017-2948 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2949 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2950 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2951 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2952 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2953 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2954 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2955 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2956 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2957 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2958 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2959 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2960 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2961 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2962 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2963 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2964 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2965 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2966 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2967 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2970 | HIGH | 7.8 | 24.01.2017 | |
| CVE-2017-2971 | HIGH | 7.8 | 24.01.2017 | |
| CVE-2017-2972 | HIGH | 7.8 | 24.01.2017 | |
| CVE-2017-3011 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3012 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3013 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3014 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3015 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3017 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3018 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3019 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3020 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3021 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3022 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3023 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3024 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3025 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3026 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3027 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3028 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3029 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3030 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3031 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3032 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3033 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3034 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3035 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3036 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3037 | CRITICAL | 9.8 | 12.04.2017 | |
| CVE-2017-3038 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3039 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3040 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3041 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3042 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3043 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3044 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3045 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3046 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3047 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3048 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3049 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3050 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3051 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3052 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3053 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3054 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3055 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3056 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3057 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3065 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2026-47911 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47912 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47913 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47914 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47959 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47961 | MEDIUM | 5.5 | 09.06.2026 |
Showing 5 out of 342.
Matched certificates
This CPE has no matched certificates.