chore(findings): tetrate/istio/operator
Summary
tetrate/istio/operator has 22 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-f3fp-gc8g-vw66 | Anchore CVE | Medium | github.com/opencontainers/runc-v1.0.2 |
GHSA-rc4r-wh2q-q6c4 | Anchore CVE | Medium | github.com/moby/moby-v17.12.0-ce-rc1.0.20200618181300-9dc6525e6118+incompatible |
CVE-2022-41715 | Twistlock CVE | High | go-1.18.4b7 |
CVE-2022-32189 | Twistlock CVE | High | go-1.18.4b7 |
CVE-2022-2880 | Twistlock CVE | High | go-1.18.4b7 |
CVE-2022-2879 | Twistlock CVE | High | go-1.18.4b7 |
CVE-2022-27664 | Twistlock CVE | High | go-1.18.4b7 |
PRISMA-2022-0270 | Twistlock CVE | Medium | github.com/golang-jwt/jwt/v4-v4.0.0 |
CVE-2022-36055 | Twistlock CVE | Medium | helm.sh/helm/v3-v3.8.0 |
CVE-2022-29162 | Twistlock CVE | Medium | github.com/opencontainers/runc-v1.0.2 |
CVE-2021-43784 | Twistlock CVE | Medium | github.com/opencontainers/runc-v1.0.2 |
GHSA-qq97-vm5h-rrhg | Twistlock CVE | Low | github.com/docker/distribution-v2.7.1 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.4b7 |
CVE-2022-32190 | Twistlock CVE | High | go-1.18.4b7 |
GHSA-vp35-85q5-9f25 | Anchore CVE | Low | github.com/moby/moby-v17.12.0-ce-rc1.0.20200618181300-9dc6525e6118+incompatible |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.4b7 |
CVE-2022-23526 | Twistlock CVE | Medium | helm.sh/helm/v3-v3.8.0 |
CVE-2022-23525 | Twistlock CVE | Medium | helm.sh/helm/v3-v3.8.0 |
CVE-2022-23524 | Twistlock CVE | Medium | helm.sh/helm/v3-v3.8.0 |
GHSA-53c4-hhmh-vw5q | Anchore CVE | Medium | helm.sh/helm/v3-v3.8.0 |
GHSA-6rx9-889q-vv2r | Anchore CVE | Medium | helm.sh/helm/v3-v3.8.0 |
GHSA-67fx-wx78-jx33 | Anchore CVE | Medium | helm.sh/helm/v3-v3.8.0 |
VAT: https://vat.dso.mil/vat/image?imageName=tetrate/istio/operator&tag=1.13.7-tetratefips-v0&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/tetrate/istio/1.13/operator/-/jobs/13079935
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"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.