chore(findings): kubeflow/mxnet/mxnet-operator-v1beta1
Summary
kubeflow/mxnet/mxnet-operator-v1beta1 has 33 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2022-21698 | Twistlock CVE | High | github.com/prometheus/client_golang-v1.5.1 |
CVE-2022-41723 | Twistlock CVE | Low | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-vvpx-j8f3-3w6h | Anchore CVE | High | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-vvpx-j8f3-3w6h | Anchore CVE | High | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-cg3q-j54f-5p7p | Anchore CVE | High | github.com/prometheus/client_golang-v1.5.1 |
CVE-2022-27664 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
CVE-2022-27191 | Twistlock CVE | High | golang.org/x/crypto-v0.0.0-20200220183623-bac4c82f6975 |
CVE-2021-43565 | Twistlock CVE | High | golang.org/x/crypto-v0.0.0-20200220183623-bac4c82f6975 |
GHSA-69cg-p879-7622 | Anchore CVE | High | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-gwc9-m7rh-j2ww | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200220183623-bac4c82f6975 |
GHSA-69cg-p879-7622 | Anchore CVE | High | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-gwc9-m7rh-j2ww | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200220183623-bac4c82f6975 |
GHSA-8c26-wmh5-6g9v | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200220183623-bac4c82f6975 |
GHSA-8c26-wmh5-6g9v | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200220183623-bac4c82f6975 |
CVE-2022-32149 | Twistlock CVE | High | golang.org/x/text-v0.3.2 |
GHSA-69ch-w2m2-3vjp | Anchore CVE | High | golang.org/x/text-v0.3.2 |
GHSA-69ch-w2m2-3vjp | Anchore CVE | High | golang.org/x/text-v0.3.2 |
CVE-2021-38561 | Twistlock CVE | High | golang.org/x/text-v0.3.2 |
CVE-2021-33194 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
CVE-2022-29526 | Twistlock CVE | Medium | golang.org/x/sys-v0.0.0-20200122134326-e047566fdf82 |
CVE-2021-31525 | Twistlock CVE | Medium | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-h86h-8ppg-mxmh | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-3vm4-22fp-5rfm | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200220183623-bac4c82f6975 |
GHSA-83g2-8m93-v3w7 | Anchore CVE | High | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-h86h-8ppg-mxmh | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-ppp9-7jff-5vj2 | Anchore CVE | High | golang.org/x/text-v0.3.2 |
GHSA-jmrx-5g74-6v2f | Anchore CVE | Medium | k8s.io/client-go-v0.16.9 |
GHSA-3vm4-22fp-5rfm | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200220183623-bac4c82f6975 |
GHSA-ppp9-7jff-5vj2 | Anchore CVE | High | golang.org/x/text-v0.3.2 |
GHSA-83g2-8m93-v3w7 | Anchore CVE | High | golang.org/x/net-v0.0.0-20200226121028-0de0cce0169b |
GHSA-jmrx-5g74-6v2f | Anchore CVE | Medium | k8s.io/client-go-v0.16.9 |
GHSA-p782-xgp4-8hr8 | Anchore CVE | Medium | golang.org/x/sys-v0.0.0-20200122134326-e047566fdf82 |
GHSA-p782-xgp4-8hr8 | Anchore CVE | Medium | golang.org/x/sys-v0.0.0-20200122134326-e047566fdf82 |
VAT: https://vat.dso.mil/vat/image?imageName=kubeflow/mxnet/mxnet-operator-v1beta1&tag=2.8.1&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/kubeflow/mxnet/mxnet-operator-v1beta1/-/jobs/19297713
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.