chore(findings): opensource/jupyter/jupyterlab
Summary
opensource/jupyter/jupyterlab has 290 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2022-48339 | Anchore CVE | Medium | emacs-filesystem-1:26.1-10.el8_8.2 |
CVE-2022-48337 | Anchore CVE | Medium | emacs-filesystem-1:26.1-10.el8_8.2 |
CVE-2023-2222 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-48338 | Anchore CVE | Medium | emacs-filesystem-1:26.1-10.el8_8.2 |
CVE-2023-31484 | Anchore CVE | Medium | perl-interpreter-4:5.26.3-422.el8 |
CVE-2023-31484 | Anchore CVE | Medium | perl-macros-4:5.26.3-422.el8 |
CVE-2023-31484 | Anchore CVE | Medium | perl-libs-4:5.26.3-422.el8 |
CVE-2023-31484 | Anchore CVE | Medium | perl-IO-0:1.38-422.el8 |
CVE-2023-31484 | Anchore CVE | Medium | perl-Errno-0:1.28-422.el8 |
GHSA-5xp3-jfq3-5q8x | Anchore CVE | Medium | pip-19.3.1 |
CVE-2018-20225 | Anchore CVE | High | pip-19.3.1 |
CVE-2023-3446 | Anchore CVE | Low | openssl-1:1.1.1k-9.el8_7 |
CVE-2023-4016 | Anchore CVE | Low | procps-ng-3.3.15-13.el8 |
CVE-2022-47008 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2020-19724 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-45703 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-48065 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47673 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47010 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2021-46174 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47696 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-48063 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-44840 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47011 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-48064 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2020-35342 | Anchore CVE | Medium | binutils-2.30-119.el8 |
CVE-2020-19726 | Anchore CVE | Medium | binutils-2.30-119.el8 |
CVE-2022-47695 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-35206 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47007 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2020-21490 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2022-35205 | Anchore CVE | Low | binutils-2.30-119.el8 |
CVE-2023-4039 | Anchore CVE | Medium | gcc-8.5.0-18.el8 |
CVE-2023-4039 | Anchore CVE | Medium | libgomp-8.5.0-18.el8 |
CVE-2023-4039 | Anchore CVE | Medium | cpp-8.5.0-18.el8 |
CVE-2023-3567 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3141 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-3534 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3611 | Anchore CVE | High | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4133 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3772 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4244 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-12656 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3773 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2021-45402 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4010 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-2513 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-20569 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-2163 | Anchore CVE | High | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-45886 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-4379 | Anchore CVE | High | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3812 | Anchore CVE | High | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-21102 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4459 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2019-19535 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3212 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-1079 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-25775 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-19186 | Anchore CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2023-40283 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-20583 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-19188 | Anchore CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2021-4204 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2019-15505 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-33203 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4881 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-31085 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-19190 | Anchore CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2023-4387 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-26545 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-31084 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-1855 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4207 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4194 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2021-3753 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-38409 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-4543 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-2176 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-23222 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-28464 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-0458 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2021-34866 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-15802 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2019-20794 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-35824 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-19185 | Anchore CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2022-45884 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-2785 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-31083 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-33952 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-27418 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-35825 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-1074 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4206 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-37453 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3161 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-31082 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-1998 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-1989 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4132 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3268 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-23908 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-10135 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-31436 | Anchore CVE | High | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-1838 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3609 | Anchore CVE | High | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-0264 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-25656 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-1075 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2019-19536 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2019-19529 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-26555 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-2248 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2019-13631 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4155 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-33951 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4622 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-2905 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4563 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-2162 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-0500 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3640 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-45885 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2019-15794 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-2166 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-42432 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-40982 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-1380 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-2483 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-2269 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-30456 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-1077 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2021-20320 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-45869 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-28772 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-35823 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3006 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-4744 | Anchore CVE | High | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-19187 | Anchore CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2021-40490 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3327 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-45887 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-28410 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-45919 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2019-14283 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2022-3424 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-3159 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-27043 | Anchore CVE | Medium | python38-libs-3.8.16-1.module+el8.8.0+18967+20d359ae.1 |
CVE-2021-21300 | Anchore CVE | Medium | git-core-doc-2.39.3-1.el8_8 |
CVE-2023-31486 | Anchore CVE | Medium | perl-HTTP-Tiny-0.074-1.el8 |
CVE-2023-1579 | Anchore CVE | Medium | binutils-2.30-119.el8 |
CVE-2020-10543 | Anchore CVE | Medium | perl-IO-0:1.38-422.el8 |
CVE-2020-10878 | Anchore CVE | Medium | perl-macros-4:5.26.3-422.el8 |
CVE-2020-12723 | Anchore CVE | Medium | perl-libs-4:5.26.3-422.el8 |
CVE-2021-40330 | Anchore CVE | Medium | git-core-doc-2.39.3-1.el8_8 |
CVE-2020-12723 | Anchore CVE | Medium | perl-macros-4:5.26.3-422.el8 |
CVE-2021-21300 | Anchore CVE | Medium | perl-Git-2.39.3-1.el8_8 |
CVE-2020-10878 | Anchore CVE | Medium | perl-IO-0:1.38-422.el8 |
CVE-2021-21300 | Anchore CVE | Medium | git-core-2.39.3-1.el8_8 |
CVE-2020-12723 | Anchore CVE | Medium | perl-IO-0:1.38-422.el8 |
CVE-2020-10543 | Anchore CVE | Medium | perl-Errno-0:1.28-422.el8 |
CVE-2020-10543 | Anchore CVE | Medium | perl-interpreter-4:5.26.3-422.el8 |
CVE-2020-12723 | Anchore CVE | Medium | perl-Errno-0:1.28-422.el8 |
CVE-2020-10878 | Anchore CVE | Medium | perl-interpreter-4:5.26.3-422.el8 |
CVE-2021-40330 | Anchore CVE | Medium | perl-Git-2.39.3-1.el8_8 |
CVE-2021-40330 | Anchore CVE | Medium | git-2.39.3-1.el8_8 |
CVE-2021-39537 | Anchore CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2023-37454 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2020-10878 | Anchore CVE | Medium | perl-libs-4:5.26.3-422.el8 |
CVE-2021-21300 | Anchore CVE | Medium | git-2.39.3-1.el8_8 |
CVE-2021-32256 | Anchore CVE | Medium | binutils-2.30-119.el8 |
CVE-2020-12723 | Anchore CVE | Medium | perl-interpreter-4:5.26.3-422.el8 |
CVE-2020-10878 | Anchore CVE | Medium | perl-Errno-0:1.28-422.el8 |
CVE-2023-27043 | Anchore CVE | Medium | python38-3.8.16-1.module+el8.8.0+18967+20d359ae.1 |
CVE-2023-0464 | Twistlock CVE | Low | openssl-1.1.1k-9.el8_7 |
CVE-2023-0466 | Twistlock CVE | Low | openssl-1.1.1k-9.el8_7 |
CVE-2023-0465 | Twistlock CVE | Low | openssl-1.1.1k-9.el8_7 |
CVE-2022-48339 | Twistlock CVE | Medium | emacs-filesystem-26.1-10.el8_8.2 |
CVE-2022-48338 | Twistlock CVE | Medium | emacs-filesystem-26.1-10.el8_8.2 |
CVE-2022-48337 | Twistlock CVE | Medium | emacs-filesystem-26.1-10.el8_8.2 |
CVE-2023-1579 | Twistlock CVE | Medium | binutils-2.30-119.el8 |
CVE-2023-1972 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2023-2650 | Twistlock CVE | Low | openssl-1.1.1k-9.el8_7 |
CVE-2023-31484 | Twistlock CVE | Medium | perl-IO-1.38-422.el8 |
CVE-2023-31484 | Twistlock CVE | Medium | perl-macros-5.26.3-422.el8 |
CVE-2023-31484 | Twistlock CVE | Medium | perl-interpreter-5.26.3-422.el8 |
CVE-2023-31484 | Twistlock CVE | Medium | perl-Errno-1.28-422.el8 |
CVE-2023-31484 | Twistlock CVE | Medium | perl-libs-5.26.3-422.el8 |
PRISMA-2022-0168 | Twistlock CVE | High | pip-19.3.1 |
CVE-2023-3446 | Twistlock CVE | Low | openssl-1.1.1k-9.el8_7 |
CVE-2023-3817 | Twistlock CVE | Low | openssl-1.1.1k-9.el8_7 |
CVE-2023-31486 | Twistlock CVE | Medium | perl-HTTP-Tiny-0.074-1.el8 |
CVE-2023-4016 | Twistlock CVE | Low | procps-ng-3.3.15-13.el8 |
CVE-2022-48065 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-48064 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-48063 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47696 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47695 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47673 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47011 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47010 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47008 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-47007 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-45703 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-44840 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-35206 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2022-35205 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2021-46174 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2020-35342 | Twistlock CVE | Medium | binutils-2.30-119.el8 |
CVE-2020-21490 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2020-19726 | Twistlock CVE | Medium | binutils-2.30-119.el8 |
CVE-2020-19724 | Twistlock CVE | Low | binutils-2.30-119.el8 |
CVE-2023-4039 | Twistlock CVE | Medium | libgomp-8.5.0-18.el8 |
CVE-2023-4039 | Twistlock CVE | Medium | cpp-8.5.0-18.el8 |
CVE-2023-4039 | Twistlock CVE | Medium | gcc-8.5.0-18.el8 |
CVE-2020-19190 | Twistlock CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2020-19189 | Twistlock CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2020-19188 | Twistlock CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2020-19187 | Twistlock CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2020-19186 | Twistlock CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2020-19185 | Twistlock CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2021-39537 | Twistlock CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2018-19211 | Twistlock CVE | Low | ncurses-6.1-9.20180224.el8_8.1 |
CVE-2020-10543 | Anchore CVE | Medium | perl-libs-4:5.26.3-422.el8 |
CVE-2020-10543 | Anchore CVE | Medium | perl-macros-4:5.26.3-422.el8 |
CVE-2021-40330 | Anchore CVE | Medium | git-core-2.39.3-1.el8_8 |
CVE-2023-42753 | Anchore CVE | High | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-42755 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-5197 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-42752 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4732 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-4610 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-5345 | Anchore CVE | High | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-42754 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-39195 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-5156 | Anchore CVE | Medium | glibc-devel-2.28-225.el8_8.6 |
CVE-2023-5156 | Anchore CVE | Medium | glibc-headers-2.28-225.el8_8.6 |
CVE-2023-39194 | Anchore CVE | Low | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-0687 | Anchore CVE | Medium | glibc-headers-2.28-225.el8_8.6 |
CVE-2023-39193 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-0687 | Anchore CVE | Medium | glibc-devel-2.28-225.el8_8.6 |
CVE-2023-39192 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-39189 | Anchore CVE | Medium | kernel-headers-4.18.0-477.27.1.el8_8 |
CVE-2023-44487 | Anchore CVE | High | nodejs-full-i18n-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2022-29244 | Anchore CVE | Medium | nodejs-full-i18n-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32559 | Anchore CVE | Medium | nodejs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2022-29244 | Anchore CVE | Medium | nodejs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32002 | Anchore CVE | High | nodejs-docs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32559 | Anchore CVE | Medium | npm-1:8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32006 | Anchore CVE | Medium | npm-1:8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32559 | Anchore CVE | Medium | nodejs-full-i18n-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-44487 | Anchore CVE | High | nodejs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32006 | Anchore CVE | Medium | nodejs-full-i18n-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32002 | Anchore CVE | High | nodejs-full-i18n-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2018-20225 | Anchore CVE | High | pip-23.3 |
CVE-2023-32002 | Anchore CVE | High | nodejs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32559 | Anchore CVE | Medium | nodejs-docs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32006 | Anchore CVE | Medium | nodejs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-44487 | Anchore CVE | High | nodejs-docs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-44487 | Anchore CVE | High | npm-1:8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2022-29244 | Anchore CVE | Medium | npm-1:8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32002 | Anchore CVE | High | npm-1:8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-32006 | Anchore CVE | Medium | nodejs-docs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2022-29244 | Anchore CVE | Medium | nodejs-docs-1:16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2022-40897 | Twistlock CVE | Medium | python38-setuptools-wheel-41.6.0-5.module+el8.5.0+12205+a865257a |
CVE-2022-40897 | Twistlock CVE | Medium | python38-setuptools-41.6.0-5.module+el8.5.0+12205+a865257a |
CVE-2021-3572 | Twistlock CVE | Medium | pip-19.3.1 |
CVE-2018-25091 | Twistlock CVE | Medium | python38-pip-wheel-19.3.1-6.module+el8.7.0+15823+8950cfa7 |
CVE-2018-25091 | Twistlock CVE | Medium | python38-pip-19.3.1-6.module+el8.7.0+15823+8950cfa7 |
CVE-2023-39332 | Twistlock CVE | Critical | nodejs-full-i18n-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-39332 | Twistlock CVE | Critical | npm-8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-39332 | Twistlock CVE | Critical | nodejs-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-39331 | Twistlock CVE | Critical | nodejs-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-39331 | Twistlock CVE | Critical | nodejs-full-i18n-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-39331 | Twistlock CVE | Critical | npm-8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-38552 | Twistlock CVE | Medium | npm-8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-38552 | Twistlock CVE | Medium | nodejs-full-i18n-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-38552 | Twistlock CVE | Medium | nodejs-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2022-29244 | Twistlock CVE | Medium | nodejs-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2022-29244 | Twistlock CVE | Medium | npm-8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2022-29244 | Twistlock CVE | Medium | nodejs-full-i18n-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-39333 | Twistlock CVE | Low | nodejs-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-39333 | Twistlock CVE | Low | npm-8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-39333 | Twistlock CVE | Low | nodejs-full-i18n-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-45143 | Twistlock CVE | Low | nodejs-full-i18n-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-45143 | Twistlock CVE | Low | nodejs-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2023-45143 | Twistlock CVE | Low | npm-8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
CVE-2017-15897 | Twistlock CVE | Low | nodejs-full-i18n-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2017-15897 | Twistlock CVE | Low | nodejs-16.20.2-3.module+el8.8.0+20386+0b1f3093 |
CVE-2017-15897 | Twistlock CVE | Low | npm-8.19.4-1.16.20.2.3.module+el8.8.0+20386+0b1f3093 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/jupyter/jupyterlab&tag=3.6.3&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/jupyter/jupyterlab&tag=3.6.3&branch=master
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Hardening::Verification" 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.