chore(findings): huron-digital-pathology/lagotto-data-gateway
Summary
huron-digital-pathology/lagotto-data-gateway has 58 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2022-35737 | Anchore CVE | Medium | sqlite-libs-3.26.0-16.el8_6 |
CVE-2022-45061 | Anchore CVE | Medium | platform-python-3.6.8-48.el8_7 |
CVE-2022-42898 | Anchore CVE | High | krb5-libs-1.18.2-21.el8 |
CVE-2022-45061 | Anchore CVE | Medium | python3-libs-3.6.8-48.el8_7 |
CVE-2022-36227 | Anchore CVE | Low | libarchive-3.3.3-4.el8 |
CVE-2021-46848 | Anchore CVE | Medium | libtasn1-4.13-3.el8 |
CVE-2007-4559 | Anchore CVE | Medium | platform-python-3.6.8-48.el8_7 |
CVE-2022-43680 | Anchore CVE | Medium | expat-2.2.5-10.el8 |
CVE-2007-4559 | Anchore CVE | Medium | python3-libs-3.6.8-48.el8_7 |
CVE-2022-4285 | Anchore CVE | Medium | gdb-gdbserver-8.2-19.el8 |
CVE-2022-4415 | Anchore CVE | Medium | systemd-libs-239-68.el8 |
CVE-2022-43552 | Anchore CVE | Low | libcurl-7.61.1-25.el8 |
CVE-2022-4415 | Anchore CVE | Medium | systemd-pam-239-68.el8 |
CVE-2022-43552 | Anchore CVE | Low | curl-7.61.1-25.el8 |
CVE-2022-4415 | Anchore CVE | Medium | systemd-239-68.el8 |
CVE-2022-40897 | Anchore CVE | Medium | python3-setuptools-wheel-39.2.0-6.el8 |
CVE-2022-40897 | Anchore CVE | Medium | platform-python-setuptools-39.2.0-6.el8 |
CVE-2022-42898 | OSCAP Compliance | Medium | |
CCE-85987-6 | OSCAP Compliance | Medium | |
CCE-84036-3 | OSCAP Compliance | Medium | |
CCE-86534-5 | OSCAP Compliance | Medium | |
CCE-85888-6 | OSCAP Compliance | Medium | |
CCE-84038-9 | OSCAP Compliance | Medium | |
CCE-86099-9 | OSCAP Compliance | Medium | |
CVE-2022-30580 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-41715 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-32189 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30635 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30633 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30632 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30631 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30630 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-2880 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-2879 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-28131 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-27664 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-32148 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2022-1705 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2022-1962 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2022-30629 | Twistlock CVE | Low | go-1.17.9 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2022-42898 | Twistlock CVE | Critical | krb5-libs-1.18.2-21.el8 |
CVE-2022-45061 | Twistlock CVE | Medium | python3-libs-3.6.8-48.el8_7 |
CVE-2022-45061 | Twistlock CVE | Medium | platform-python-3.6.8-48.el8_7 |
CVE-2022-36227 | Twistlock CVE | Low | libarchive-3.3.3-4.el8 |
CVE-2022-4285 | Twistlock CVE | Medium | gdb-gdbserver-8.2-19.el8 |
CVE-2022-46908 | Twistlock CVE | Medium | sqlite-libs-3.26.0-16.el8_6 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2022-4415 | Twistlock CVE | Medium | systemd-pam-239-68.el8 |
CVE-2022-4415 | Twistlock CVE | Medium | systemd-libs-239-68.el8 |
CVE-2022-4415 | Twistlock CVE | Medium | systemd-239-68.el8 |
CVE-2022-43552 | Twistlock CVE | Low | libcurl-7.61.1-25.el8 |
CVE-2022-43552 | Twistlock CVE | Low | curl-7.61.1-25.el8 |
CVE-2022-45873 | Twistlock CVE | Medium | systemd-239-68.el8 |
CVE-2022-45873 | Twistlock CVE | Medium | systemd-libs-239-68.el8 |
CVE-2022-45873 | Twistlock CVE | Medium | systemd-pam-239-68.el8 |
CVE-2022-40897 | Twistlock CVE | Medium | platform-python-setuptools-39.2.0-6.el8 |
CVE-2022-40897 | Twistlock CVE | Medium | python3-setuptools-wheel-39.2.0-6.el8 |
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/huron-digital-pathology/lagotto-data-gateway/-/jobs/23484126
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.