chore(findings): pytorch-operator/pytorch-operator
Summary
pytorch-operator/pytorch-operator has 21 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2023-28321 | Anchore CVE | Medium | libcurl-7.61.1-30.el8_8.2 |
CVE-2023-28321 | Anchore CVE | Medium | curl-7.61.1-30.el8_8.2 |
CVE-2023-32681 | Anchore CVE | Medium | python3-requests-2.20.0-2.1.el8_1 |
CVE-2023-2953 | Anchore CVE | Low | openldap-2.4.46-18.el8 |
CVE-2023-2603 | Anchore CVE | Medium | libcap-2.48-4.el8 |
CVE-2023-2602 | Anchore CVE | Low | libcap-2.48-4.el8 |
CVE-2023-30571 | Anchore CVE | Medium | libarchive-3.3.3-5.el8 |
CVE-2023-34969 | Anchore CVE | Medium | dbus-daemon-1:1.12.8-24.el8 |
CVE-2023-34969 | Anchore CVE | Medium | dbus-common-1:1.12.8-24.el8 |
CVE-2023-34969 | Anchore CVE | Medium | dbus-libs-1:1.12.8-24.el8 |
CVE-2023-34969 | Anchore CVE | Medium | dbus-1:1.12.8-24.el8 |
CVE-2023-34969 | Anchore CVE | Medium | dbus-tools-1:1.12.8-24.el8 |
CVE-2023-27043 | Anchore CVE | Medium | platform-python-3.6.8-51.el8_8.1 |
CVE-2007-4559 | Anchore CVE | Medium | platform-python-3.6.8-51.el8_8.1 |
CVE-2007-4559 | Anchore CVE | Medium | python3-libs-3.6.8-51.el8_8.1 |
CVE-2023-27043 | Anchore CVE | Medium | python3-libs-3.6.8-51.el8_8.1 |
CVE-2023-32681 | Twistlock CVE | Medium | requests-2.20.0 |
CVE-2023-24329 | Twistlock CVE | Critical | python3-libs-3.6.8-51.el8_8.1 |
CVE-2023-24329 | Twistlock CVE | Critical | platform-python-3.6.8-51.el8_8.1 |
CVE-2019-9674 | Twistlock CVE | Low | python3-libs-3.6.8-51.el8_8.1 |
CVE-2019-9674 | Twistlock CVE | Low | platform-python-3.6.8-51.el8_8.1 |
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/kubeflow/pytorch/pytorch-operator-v0.6.0-18-g5e36a57/-/jobs/22530679
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.