This page was not yet optimized for use on mobile devices.
Adobe Acrobat Document Cloud (DC) 15.000.0000 Classic Track
Configuration details
| CPE title | Adobe Acrobat Document Cloud (DC) 15.000.0000 Classic Track |
|---|---|
| URI | cpe:2.3:a:adobe:acrobat_dc:15.000.0000:*:*:*:classic:*:*:* |
Linked CVEs
234 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| 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-3009 | HIGH | 7.5 | 31.03.2017 | |
| CVE-2017-3010 | CRITICAL | 9.8 | 31.03.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-3016 | HIGH | 8.8 | 11.08.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-2017-3113 | HIGH | 8.8 | 11.08.2017 | |
| CVE-2017-3115 | MEDIUM | 6.5 | 11.08.2017 | |
| CVE-2017-3116 | HIGH | 8.8 | 11.08.2017 | |
| CVE-2017-3117 | HIGH | 8.8 | 11.08.2017 | |
| CVE-2017-3118 | MEDIUM | 6.5 | 11.08.2017 | |
| CVE-2017-3119 | HIGH | 8.8 | 11.08.2017 | |
| CVE-2017-3120 | HIGH | 8.8 | 11.08.2017 | |
| CVE-2017-3121 | HIGH | 8.8 | 11.08.2017 | |
| CVE-2017-3122 | MEDIUM | 6.5 | 11.08.2017 | |
| CVE-2017-3123 | HIGH | 8.8 | 11.08.2017 | |
| CVE-2017-3124 | CRITICAL | 9.8 | 11.08.2017 | |
| CVE-2018-4872 | CRITICAL | 10.0 | 27.02.2018 | |
| CVE-2018-4879 | CRITICAL | 9.8 | 27.02.2018 | |
| CVE-2018-4880 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4881 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4882 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4883 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4884 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4885 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4886 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4887 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4888 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4889 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4890 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4891 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4892 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4893 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4894 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4895 | CRITICAL | 9.8 | 27.02.2018 | |
| CVE-2018-4896 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4897 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4898 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4899 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4900 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4901 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4902 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4903 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4904 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4905 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4906 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4907 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4908 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4909 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4910 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4911 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4912 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4913 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4914 | MEDIUM | 6.5 | 27.02.2018 | |
| CVE-2018-4915 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2018-4916 | HIGH | 8.8 | 27.02.2018 | |
| CVE-2019-7819 | MEDIUM | 5.5 | 11.09.2023 | |
| CVE-2020-24426 | LOW | 3.3 | 05.11.2020 | |
| CVE-2020-24427 | LOW | 3.3 | 05.11.2020 | |
| CVE-2020-24428 | HIGH | 7.7 | 05.11.2020 | |
| CVE-2020-24429 | HIGH | 7.8 | 05.11.2020 | |
| CVE-2020-24430 | HIGH | 7.8 | 05.11.2020 | |
| CVE-2020-24431 | MEDIUM | 4.4 | 05.11.2020 | |
| CVE-2020-24432 | HIGH | 7.8 | 05.11.2020 | |
| CVE-2020-24433 | HIGH | 7.8 | 05.11.2020 | |
| CVE-2020-24434 | LOW | 3.3 | 05.11.2020 | |
| CVE-2020-24435 | HIGH | 7.8 | 05.11.2020 | |
| CVE-2020-24436 | HIGH | 7.8 | 05.11.2020 | |
| CVE-2020-24437 | HIGH | 7.8 | 05.11.2020 | |
| CVE-2020-24438 | LOW | 3.3 | 05.11.2020 | |
| CVE-2020-24439 | LOW | 2.8 | 05.11.2020 | |
| CVE-2020-9695 | HIGH | 7.8 | 23.06.2026 | |
| CVE-2020-9711 | MEDIUM | 5.5 | 23.06.2026 | |
| CVE-2020-9713 | MEDIUM | 5.5 | 23.06.2026 |
Showing 5 out of 234.
Matched certificates
This CPE has no matched certificates.