chore(findings): blackduck/codedx/codedx-docker-tomcat-base
Summary
blackduck/codedx/codedx-docker-tomcat-base has 259 new findings discovered during continuous monitoring.
Layer: opensource/apache/tomcat9-openjdk11:9.0.106 is EOL, please update if possible
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=blackduck/codedx/codedx-docker-tomcat-base&tag=1.15.0&branch=master
EPSS (Exploit Prediction Scoring System) provides an estimate of the likelihood that a vulnerability will be exploited in the wild.
KEV (Known Exploited Vulnerabilities) indicates whether a vulnerability is actively being exploited according to CISA.
id | source | severity | package | impact | workaround | epss_score | kev |
---|---|---|---|---|---|---|---|
CVE-2018-19210 | Twistlock CVE | Low | libtiff-4.0.9-34.el8_10 | 0.05546 | false | ||
CVE-2018-19210 | Anchore CVE | Low | libtiff-4.0.9-34.el8_10 | 0.05546 | false | ||
CVE-2022-48565 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.03703 | false | ||
CVE-2022-48565 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.03703 | false | ||
CVE-2019-6128 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.02457 | false | ||
CVE-2019-6128 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.02457 | false | ||
CVE-2019-2201 | Twistlock CVE | Medium | libjpeg-turbo-1.5.3-14.el8_10 | 0.02060 | false | ||
CVE-2019-2201 | Anchore CVE | Medium | libjpeg-turbo-1.5.3-14.el8_10 | 0.02060 | false | ||
CVE-2019-7164 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.01979 | false | ||
CVE-2019-7164 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.01979 | false | ||
CVE-2019-11324 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.01571 | false | ||
CVE-2019-11324 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.01571 | false | ||
CVE-2018-16335 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.01466 | false | ||
CVE-2018-16335 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.01466 | false | ||
CVE-2019-9674 | Anchore CVE | Low | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.01258 | false | ||
CVE-2019-7548 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.01109 | false | ||
CVE-2019-7548 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.01109 | false | ||
CVE-2018-20030 | Anchore CVE | Low | libexif-0.6.22-5.el8_3 | 0.01058 | false | ||
CVE-2018-20030 | Twistlock CVE | Low | libexif-0.6.22-5.el8_3 | 0.01058 | false | ||
CVE-2018-20225 | Anchore CVE | Low | python3-pip-9.0.3-24.el8 | 0.01017 | false | ||
CVE-2018-20060 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.00949 | false | ||
CVE-2018-20060 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.00949 | false | ||
CVE-2022-0391 | Anchore CVE | Medium | python39-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00816 | false | ||
CVE-2022-0391 | Anchore CVE | Medium | python39-libs-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00816 | false | ||
CVE-2019-11236 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.00636 | false | ||
CVE-2019-11236 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.00636 | false | ||
CVE-2025-0938 | Anchore CVE | Medium | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00624 | false | ||
CVE-2025-0938 | Anchore CVE | Medium | python39-libs-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00624 | false | ||
CVE-2025-0938 | Anchore CVE | Medium | python39-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00624 | false | ||
CVE-2018-18064 | Twistlock CVE | Medium | cairo-1.15.12-6.el8 | 0.00507 | false | ||
CVE-2018-18064 | Anchore CVE | Medium | cairo-1.15.12-6.el8 | 0.00507 | false | ||
CVE-2018-17101 | Twistlock CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00504 | false | ||
CVE-2018-17101 | Anchore CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00504 | false | ||
CVE-2024-7592 | Anchore CVE | Low | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00468 | false | ||
CVE-2024-7592 | Anchore CVE | Low | python39-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00468 | false | ||
CVE-2024-7592 | Anchore CVE | Low | python39-libs-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00468 | false | ||
CVE-2018-5360 | Twistlock CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00459 | false | ||
CVE-2018-5360 | Anchore CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00459 | false | ||
CVE-2023-40745 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00425 | false | ||
CVE-2023-40745 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00425 | false | ||
CVE-2023-6277 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00418 | false | ||
CVE-2023-6277 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00418 | false | ||
CVE-2018-10801 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00403 | false | ||
CVE-2018-10801 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00403 | false | ||
CVE-2021-3733 | Anchore CVE | Medium | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00370 | false | ||
CVE-2024-3651 | Twistlock CVE | Medium | python-urllib3-1.24.2-8.el8_10 | 0.00347 | false | ||
CVE-2024-3651 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.00347 | false | ||
CVE-2024-3651 | Twistlock CVE | Medium | python-requests-2.20.0-5.el8_10 | 0.00347 | false | ||
CVE-2024-3651 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.00347 | false | ||
CVE-2023-41175 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00315 | false | ||
CVE-2023-41175 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00315 | false | ||
CVE-2018-19876 | Anchore CVE | Low | cairo-1.15.12-6.el8 | 0.00303 | false | ||
CVE-2018-19876 | Twistlock CVE | Low | cairo-1.15.12-6.el8 | 0.00303 | false | ||
CVE-2022-2255 | Twistlock CVE | Medium | python-idna-2.5-7.el8_10 | 0.00266 | false | ||
CVE-2022-2255 | Twistlock CVE | Medium | python-urllib3-1.24.2-8.el8_10 | 0.00266 | false | ||
CVE-2022-2255 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.00266 | false | ||
CVE-2022-2255 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.00266 | false | ||
CVE-2022-2255 | Twistlock CVE | Medium | python-requests-2.20.0-5.el8_10 | 0.00266 | false | ||
CVE-2018-10779 | Twistlock CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00255 | false | ||
CVE-2018-10779 | Anchore CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00255 | false | ||
CVE-2024-0397 | Anchore CVE | Low | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00232 | false | ||
CVE-2024-0397 | Anchore CVE | Low | python39-libs-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00232 | false | ||
CVE-2024-0397 | Anchore CVE | Low | python39-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00232 | false | ||
CVE-2022-0529 | Twistlock CVE | Low | unzip-6.0-48.el8_10 | 0.00230 | false | ||
CVE-2022-0529 | Anchore CVE | Low | unzip-6.0-48.el8_10 | 0.00230 | false | ||
CVE-2023-25434 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00209 | false | ||
CVE-2023-25434 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00209 | false | ||
CVE-2025-53506 | Twistlock CVE | Medium | tomcat-coyote-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-dbcp-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-i18n-es-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-i18n-ru-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-i18n-cs-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-juli-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-i18n-fr-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-i18n-ja-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-i18n-ko-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-api-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-i18n-de-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-websocket-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-jni-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-jdbc-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-util-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Anchore CVE | High | tomcat-util-scan-9.0.106 | 0.00195 | false | ||
CVE-2025-53506 | Twistlock CVE | Low | tomcat-util-9.0.106 | 0.00195 | false | ||
CVE-2023-3618 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00183 | false | ||
CVE-2023-3618 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00183 | false | ||
CVE-2025-52434 | Twistlock CVE | Low | tomcat-util-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-jni-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-util-scan-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-juli-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-i18n-ja-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-i18n-de-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-websocket-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-jdbc-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-dbcp-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-i18n-es-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-i18n-ru-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-coyote-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-i18n-cs-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-api-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-i18n-fr-9.0.106 | 0.00179 | false | ||
CVE-2025-52434 | Anchore CVE | High | tomcat-i18n-ko-9.0.106 | 0.00179 | false | ||
CVE-2023-32636 | Anchore CVE | Low | glib2-devel-2.56.4-166.el8_10 | 0.00179 | false | ||
CVE-2024-0450 | Twistlock CVE | Medium | python-idna-2.5-7.el8_10 | 0.00177 | false | ||
CVE-2024-0450 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.00177 | false | ||
CVE-2024-0450 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.00177 | false | ||
CVE-2024-0450 | Twistlock CVE | Medium | python-requests-2.20.0-5.el8_10 | 0.00177 | false | ||
CVE-2024-0450 | Twistlock CVE | Medium | python-urllib3-1.24.2-8.el8_10 | 0.00177 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-i18n-ko-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-i18n-de-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-jni-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-i18n-ja-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-util-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-websocket-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-juli-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-api-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-i18n-fr-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-i18n-ru-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-util-scan-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-dbcp-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-jdbc-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-coyote-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-i18n-es-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | catalina-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-i18n-cs-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.106 | 0.00164 | false | ||
CVE-2025-52520 | Twistlock CVE | Low | tomcat-util-9.0.106 | 0.00164 | false | ||
CVE-2019-6461 | Anchore CVE | Medium | cairo-1.15.12-6.el8 | 0.00154 | false | ||
CVE-2019-6461 | Twistlock CVE | Medium | cairo-1.15.12-6.el8 | 0.00154 | false | ||
CVE-2025-1795 | Anchore CVE | Low | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00140 | false | ||
CVE-2025-1795 | Anchore CVE | Low | python39-libs-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00140 | false | ||
CVE-2025-1795 | Anchore CVE | Low | python39-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00140 | false | ||
CVE-2025-47273 | Twistlock CVE | Medium | setuptools-50.3.2 | 0.00139 | false | ||
CVE-2021-4217 | Twistlock CVE | Low | unzip-6.0-48.el8_10 | 0.00134 | false | ||
CVE-2021-4217 | Anchore CVE | Low | unzip-6.0-48.el8_10 | 0.00134 | false | ||
CVE-2023-29499 | Anchore CVE | Low | glib2-devel-2.56.4-166.el8_10 | 0.00120 | false | ||
CVE-2022-0530 | Twistlock CVE | Low | unzip-6.0-48.el8_10 | 0.00120 | false | ||
CVE-2022-0530 | Anchore CVE | Low | unzip-6.0-48.el8_10 | 0.00120 | false | ||
CVE-2023-52355 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00119 | false | ||
CVE-2023-52355 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00119 | false | ||
CVE-2023-27043 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.00117 | false | ||
CVE-2023-27043 | Twistlock CVE | Medium | python-urllib3-1.24.2-8.el8_10 | 0.00117 | false | ||
CVE-2023-27043 | Twistlock CVE | Medium | python-requests-2.20.0-5.el8_10 | 0.00117 | false | ||
CVE-2023-27043 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.00117 | false | ||
CVE-2023-27043 | Twistlock CVE | Medium | python-idna-2.5-7.el8_10 | 0.00117 | false | ||
CVE-2022-48560 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.00114 | false | ||
CVE-2022-48560 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.00114 | false | ||
CVE-2021-3737 | Anchore CVE | Low | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00105 | false | ||
CVE-2024-6923 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.00089 | false | ||
CVE-2024-6923 | Twistlock CVE | Medium | python-urllib3-1.24.2-8.el8_10 | 0.00089 | false | ||
CVE-2024-6923 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.00089 | false | ||
CVE-2024-6923 | Twistlock CVE | Medium | python-requests-2.20.0-5.el8_10 | 0.00089 | false | ||
CVE-2024-6923 | Twistlock CVE | Medium | python-idna-2.5-7.el8_10 | 0.00089 | false | ||
CVE-2024-8088 | Anchore CVE | Medium | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00087 | false | ||
CVE-2024-8088 | Twistlock CVE | Medium | python-idna-2.5-7.el8_10 | 0.00087 | false | ||
CVE-2024-8088 | Twistlock CVE | Medium | python-urllib3-1.24.2-8.el8_10 | 0.00087 | false | ||
CVE-2024-8088 | Twistlock CVE | Medium | python-requests-2.20.0-5.el8_10 | 0.00087 | false | ||
CVE-2024-8088 | Twistlock CVE | Medium | python-chardet-3.0.4-7.el8 | 0.00087 | false | ||
CVE-2024-8088 | Twistlock CVE | Medium | python-pysocks-1.6.8-3.el8 | 0.00087 | false | ||
CVE-2025-3360 | Anchore CVE | Low | glib2-devel-2.56.4-166.el8_10 | 0.00079 | false | ||
CVE-2025-6069 | Anchore CVE | Medium | python39-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00077 | false | ||
CVE-2025-6069 | Anchore CVE | Medium | python39-libs-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00077 | false | ||
CVE-2025-6069 | Anchore CVE | Medium | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00077 | false | ||
CVE-2025-8194 | Anchore CVE | Medium | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00068 | false | ||
CVE-2025-8194 | Anchore CVE | Medium | python39-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00068 | false | ||
CVE-2025-8194 | Anchore CVE | Medium | python39-libs-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00068 | false | ||
CVE-2023-30086 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00063 | false | ||
CVE-2023-30086 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00063 | false | ||
CVE-2023-32665 | Anchore CVE | Low | glib2-devel-2.56.4-166.el8_10 | 0.00059 | false | ||
CVE-2023-30775 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00053 | false | ||
CVE-2023-30775 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00053 | false | ||
CVE-2019-6462 | Anchore CVE | Medium | cairo-1.15.12-6.el8 | 0.00052 | false | ||
CVE-2019-6462 | Twistlock CVE | Medium | cairo-1.15.12-6.el8 | 0.00052 | false | ||
CVE-2023-5752 | Twistlock CVE | Low | pip-20.2.4 | Only users using Mercurial VCS functionality with untrusted inputs are affected. | 0.00045 | false | |
CVE-2022-1056 | Twistlock CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00042 | false | ||
CVE-2022-1056 | Anchore CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00042 | false | ||
CVE-2025-26646 | Twistlock CVE | High | microsoft.build.tasks.core-17.0.4 | 0.00040 | false | ||
CVE-2025-26646 | Twistlock CVE | High | microsoft.build.tasks.core-17.0.4 | 0.00040 | false | ||
CVE-2025-26646 | Twistlock CVE | High | microsoft.build.tasks.core-17.0.4 | 0.00040 | false | ||
CVE-2025-26646 | Twistlock CVE | High | microsoft.build.tasks.core-17.0.4 | 0.00040 | false | ||
CVE-2025-26646 | Twistlock CVE | High | microsoft.build.tasks.core-17.0.4 | 0.00040 | false | ||
CVE-2023-32611 | Anchore CVE | Low | glib2-devel-2.56.4-166.el8_10 | 0.00037 | false | ||
CVE-2023-24056 | Anchore CVE | Low | libpkgconf-1.4.2-1.el8 | 0.00037 | false | ||
CVE-2023-24056 | Anchore CVE | Low | pkgconf-1.4.2-1.el8 | 0.00037 | false | ||
CVE-2023-24056 | Anchore CVE | Low | pkgconf-m4-1.4.2-1.el8 | 0.00037 | false | ||
CVE-2023-24056 | Anchore CVE | Low | pkgconf-pkg-config-1.4.2-1.el8 | 0.00037 | false | ||
CVE-2023-24056 | Twistlock CVE | Low | pkgconf-1.4.2-1.el8 | 0.00037 | false | ||
CVE-2023-25435 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00033 | false | ||
CVE-2023-25435 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00033 | false | ||
CVE-2022-3598 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00032 | false | ||
CVE-2022-3598 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00032 | false | ||
CVE-2023-48161 | Anchore CVE | Medium | giflib-5.1.4-3.el8 | 0.00029 | false | ||
CVE-2023-48161 | Twistlock CVE | Medium | giflib-5.1.4-3.el8 | 0.00029 | false | ||
CVE-2023-30774 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00028 | false | ||
CVE-2023-30774 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00028 | false | ||
CVE-2022-1354 | Twistlock CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00027 | false | ||
CVE-2022-1354 | Anchore CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00027 | false | ||
CVE-2023-26966 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00024 | false | ||
CVE-2023-26966 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00024 | false | ||
CVE-2022-3599 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00024 | false | ||
CVE-2022-3599 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00024 | false | ||
CVE-2020-18768 | Twistlock CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00024 | false | ||
CVE-2020-18768 | Anchore CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00024 | false | ||
CVE-2025-4516 | Anchore CVE | Medium | python39-libs-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00021 | false | ||
CVE-2025-4516 | Anchore CVE | Medium | python36-3.6.8-39.module+el8.10.0+20784+edafcd43 | 0.00021 | false | ||
CVE-2025-4516 | Anchore CVE | Medium | python39-3.9.20-1.module+el8.10.0+22342+478c159e | 0.00021 | false | ||
CVE-2023-3576 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00020 | false | ||
CVE-2023-3576 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00020 | false | ||
CVE-2023-3316 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00020 | false | ||
CVE-2023-3316 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00020 | false | ||
CVE-2023-39742 | Anchore CVE | Low | giflib-5.1.4-3.el8 | 0.00019 | false | ||
CVE-2023-39742 | Twistlock CVE | Low | giflib-5.1.4-3.el8 | 0.00019 | false | ||
CVE-2025-31344 | Anchore CVE | Medium | giflib-5.1.4-3.el8 | 0.00017 | false | ||
CVE-2025-31344 | Twistlock CVE | Medium | giflib-5.1.4-3.el8 | 0.00017 | false | ||
CVE-2023-1916 | Twistlock CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00017 | false | ||
CVE-2023-1916 | Anchore CVE | Low | libtiff-4.0.9-34.el8_10 | 0.00017 | false | ||
CVE-2020-35538 | Twistlock CVE | Low | libjpeg-turbo-1.5.3-14.el8_10 | 0.00017 | false | ||
CVE-2020-35538 | Anchore CVE | Low | libjpeg-turbo-1.5.3-14.el8_10 | 0.00017 | false | ||
CVE-2023-0795 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00015 | false | ||
CVE-2023-0795 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00015 | false | ||
CVE-2025-8177 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00014 | false | ||
CVE-2025-8177 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00014 | false | ||
CVE-2025-8176 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00014 | false | ||
CVE-2025-8176 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00014 | false | ||
CVE-2025-50181 | Anchore CVE | Medium | python3-pip-9.0.3-24.el8 | 0.00013 | false | ||
CVE-2023-0799 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00012 | false | ||
CVE-2023-0799 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00012 | false | ||
CVE-2022-40090 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00012 | false | ||
CVE-2022-40090 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00012 | false | ||
CVE-2025-50182 | Anchore CVE | Medium | python3-pip-9.0.3-24.el8 | 0.00011 | false | ||
CVE-2023-0798 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00011 | false | ||
CVE-2023-0798 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00011 | false | ||
CVE-2023-0797 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00011 | false | ||
CVE-2023-0797 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00011 | false | ||
CVE-2023-0796 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00011 | false | ||
CVE-2023-0796 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00011 | false | ||
CVE-2023-3164 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00010 | false | ||
CVE-2023-3164 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00010 | false | ||
CVE-2023-26965 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00008 | false | ||
CVE-2023-26965 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00008 | false | ||
CVE-2022-3570 | Twistlock CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00005 | false | ||
CVE-2022-3570 | Anchore CVE | Medium | libtiff-4.0.9-34.el8_10 | 0.00005 | false | ||
CVE-2022-3555 | Anchore CVE | Low | libX11-common-1.6.8-9.el8_10 | N/A | false | ||
CVE-2022-3555 | Anchore CVE | Low | libX11-1.6.8-9.el8_10 | N/A | false | ||
CVE-2022-3554 | Anchore CVE | Medium | libX11-1.6.8-9.el8_10 | N/A | false | ||
CVE-2022-3554 | Anchore CVE | Medium | libX11-common-1.6.8-9.el8_10 | N/A | false | ||
PRISMA-2022-0168 | Twistlock CVE | High | pip-20.2.4 | N/A | N/A | ||
GHSA-h4j7-5rxr-p4wc | Anchore CVE | High | Microsoft.Build.Tasks.Core-17.0.4 | N/A | N/A | ||
GHSA-h4j7-5rxr-p4wc | Anchore CVE | High | Microsoft.Build.Tasks.Core-17.0.4 | N/A | N/A | ||
GHSA-7jgj-8wvc-jh57 | Anchore CVE | High | System.Net.Http-4.3.0 | N/A | N/A | ||
GHSA-68w7-72jg-6qpp | Anchore CVE | Critical | NuGet.Packaging-6.0.6-rc.32767 | N/A | N/A | ||
GHSA-4j3c-42xv-3f84 | Anchore CVE | Medium | tomcat-util-9.0.106 | N/A | N/A | ||
GHSA-2865-hh9g-w894 | Anchore CVE | High | Microsoft.AspNetCore.App.Runtime.linux-x64-6.0.36 | N/A | N/A | ||
GHSA-25xr-qj8w-c4vf | Anchore CVE | Medium | tomcat-coyote-9.0.106 | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=blackduck/codedx/codedx-docker-tomcat-base&tag=1.15.0&branch=master
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the StatusVerification label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications
Note: If the above process is rejected for any reason, the
Verification
label will be removed and the issue will be sent back toOpen
. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theVerification
label.
Questions?
Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add /cc @ironbank-notifications/onboarding
.
Additionally, Iron Bank hosts an AMA working session every Wednesday from 1630-1730EST to answer questions.