chore(findings): opensource/jupyter/jupyterlab
Summary
opensource/jupyter/jupyterlab has 162 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2022-39260 | Twistlock CVE | Medium | git-2.31.1-2.el8 |
CVE-2022-39260 | Twistlock CVE | Medium | perl-Git-2.31.1-2.el8 |
CVE-2022-39260 | Twistlock CVE | Medium | git-core-2.31.1-2.el8 |
CVE-2021-44906 | Twistlock CVE | Medium | nodejs-16.17.1-1.module+el8.6.0+16848+a483195a |
CVE-2021-44906 | Twistlock CVE | Medium | nodejs-full-i18n-16.17.1-1.module+el8.6.0+16848+a483195a |
CVE-2021-44906 | Twistlock CVE | Medium | npm-8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a |
CVE-2021-3114 | Twistlock CVE | Medium | cpp-8.5.0-15.el8 |
CVE-2022-0235 | Twistlock CVE | Medium | nodejs-16.17.1-1.module+el8.6.0+16848+a483195a |
CVE-2022-0235 | Twistlock CVE | Medium | nodejs-full-i18n-16.17.1-1.module+el8.6.0+16848+a483195a |
CVE-2022-0235 | Twistlock CVE | Medium | npm-8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a |
CVE-2022-39253 | Twistlock CVE | Medium | perl-Git-2.31.1-2.el8 |
CVE-2022-39253 | Twistlock CVE | Medium | git-2.31.1-2.el8 |
CVE-2022-39253 | Twistlock CVE | Medium | git-core-2.31.1-2.el8 |
CVE-2021-3826 | Twistlock CVE | Low | libgomp-8.5.0-15.el8 |
CVE-2021-3826 | Twistlock CVE | Low | cpp-8.5.0-15.el8 |
CVE-2022-27943 | Twistlock CVE | Low | libgomp-8.5.0-15.el8 |
CVE-2022-27943 | Twistlock CVE | Low | gcc-8.5.0-15.el8 |
CVE-2022-27943 | Twistlock CVE | Low | cpp-8.5.0-15.el8 |
CVE-2017-15897 | Twistlock CVE | Low | npm-8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a |
CVE-2017-15897 | Twistlock CVE | Low | nodejs-16.17.1-1.module+el8.6.0+16848+a483195a |
CVE-2017-15897 | Twistlock CVE | Low | nodejs-full-i18n-16.17.1-1.module+el8.6.0+16848+a483195a |
CVE-2021-46195 | Twistlock CVE | Low | gcc-8.5.0-15.el8 |
CVE-2021-46195 | Twistlock CVE | Low | cpp-8.5.0-15.el8 |
CVE-2021-46195 | Twistlock CVE | Low | libgomp-8.5.0-15.el8 |
CVE-2019-14250 | Twistlock CVE | Low | libgomp-8.5.0-15.el8 |
CVE-2019-14250 | Twistlock CVE | Low | gcc-8.5.0-15.el8 |
CVE-2019-14250 | Twistlock CVE | Low | cpp-8.5.0-15.el8 |
CVE-2018-20657 | Twistlock CVE | Low | libgomp-8.5.0-15.el8 |
CVE-2018-20657 | Twistlock CVE | Low | cpp-8.5.0-15.el8 |
CVE-2018-20657 | Twistlock CVE | Low | gcc-8.5.0-15.el8 |
CVE-2020-28097 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1972 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-3435 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-25645 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-21233 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-20166 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-0886 | Anchore CVE | High | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-42720 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-3707 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-27950 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-38096 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-3714 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-14390 | Anchore CVE | Low | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-0171 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-41218 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-33624 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1016 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-26373 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1184 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-33656 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-14416 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39260 | Anchore CVE | Medium | git-core-2.31.1-2.el8 |
CVE-2022-3344 | Anchore CVE | Low | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39260 | Anchore CVE | Medium | perl-Git-2.31.1-2.el8 |
CVE-2022-1158 | Anchore CVE | High | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-29581 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-36557 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2586 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-28972 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-3640 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-0854 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2153 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39260 | Anchore CVE | Medium | git-2.31.1-2.el8 |
CVE-2020-27170 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-36311 | Anchore CVE | Low | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-23960 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-43975 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1048 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39253 | Anchore CVE | Medium | git-core-2.31.1-2.el8 |
CVE-2022-2602 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-30594 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-34693 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2905 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-41674 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-34981 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1263 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-29657 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-28390 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-10741 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-0617 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-30002 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2019-15213 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-33655 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2785 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-21499 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-36516 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2019-15219 | Anchore CVE | Low | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2938 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2078 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-38198 | Anchore CVE | Low | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-40133 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2663 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-42703 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1055 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-3896 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-3239 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-36402 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-38457 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1462 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1665 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-42721 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-0168 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2964 | Anchore CVE | High | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1280 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39253 | Anchore CVE | Medium | git-2.31.1-2.el8 |
CVE-2022-27943 | Anchore CVE | Low | gcc-8.5.0-15.el8 |
CVE-2022-25265 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-3826 | Anchore CVE | Low | binutils-2.30-117.el8 |
CVE-2021-3178 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-42722 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1789 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-3702 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-3586 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-4135 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-46778 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1852 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39188 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-3424 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-35501 | Anchore CVE | Low | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-36879 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-29374 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-36280 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-3444 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-20368 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39260 | Anchore CVE | Medium | git-core-doc-2.31.1-2.el8 |
CVE-2022-20141 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-38533 | Anchore CVE | Low | binutils-2.30-117.el8 |
CVE-2021-34556 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39189 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-24448 | Anchore CVE | Low | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-28893 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-27171 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2020-36558 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-3303 | Anchore CVE | Low | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-38166 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-3640 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2019-19530 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-27943 | Anchore CVE | Low | cpp-8.5.0-15.el8 |
CVE-2022-27943 | Anchore CVE | Low | libgomp-8.5.0-15.el8 |
CVE-2021-26341 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39253 | Anchore CVE | Medium | perl-Git-2.31.1-2.el8 |
CVE-2021-35477 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-38206 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-36946 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-4159 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-28693 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-3655 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2873 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-4001 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-3028 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-1679 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2019-20095 | Anchore CVE | Low | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-39253 | Anchore CVE | Medium | git-core-doc-2.31.1-2.el8 |
CVE-2022-39190 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2022-2639 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CVE-2021-3428 | Anchore CVE | Medium | kernel-headers-4.18.0-425.3.1.el8 |
CCE-86534-5 | OSCAP Compliance | Medium | |
CCE-85888-6 | OSCAP Compliance | Medium | |
CVE-2022-3517 | Twistlock CVE | Medium | nodejs-16.17.1-1.module+el8.6.0+16848+a483195a |
CVE-2022-3517 | Twistlock CVE | Medium | npm-8.15.0-1.16.17.1.1.module+el8.6.0+16848+a483195a |
CVE-2022-3517 | Twistlock CVE | Medium | nodejs-full-i18n-16.17.1-1.module+el8.6.0+16848+a483195a |
CVE-2022-23990 | Twistlock CVE | Low | expat-2.2.5-10.el8 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/jupyter/jupyterlab&tag=3.5.0&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/opensource/jupyter/jupyterlab/-/jobs/14724294
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Hardening::Approval" label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications -
Send approval request to Authorizing Official -
Close issue after approval from Authorizing Official
Note: If the above approval process is rejected for any reason, the
Approval
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 theApproval
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.