UNCLASSIFIED - NO CUI

chore(findings): tetrate/istio/proxyv2

Summary

tetrate/istio/proxyv2 has 25 new findings discovered during continuous monitoring.

id source severity package
GHSA-vvpx-j8f3-3w6h Anchore CVE High golang.org/x/net-v0.0.0-20220624214902-1bab6f366d9e
GHSA-69cg-p879-7622 Anchore CVE High golang.org/x/net-v0.0.0-20220624214902-1bab6f366d9e
GHSA-69ch-w2m2-3vjp Anchore CVE High golang.org/x/text-v0.3.7
GHSA-fxg5-wq6x-vr4w Anchore CVE High golang.org/x/net-v0.0.0-20220624214902-1bab6f366d9e
GHSA-232p-vwff-86mp Anchore CVE High github.com/docker/docker-v20.10.17+incompatible
GHSA-6wrf-mxfj-pf5p Anchore CVE Medium github.com/docker/docker-v20.10.17+incompatible
GHSA-33pg-m6jh-5237 Anchore CVE Medium github.com/docker/docker-v20.10.17+incompatible
CVE-2022-41723 Twistlock CVE High golang.org/x/net-v0.0.0-20220624214902-1bab6f366d9e
CVE-2022-27664 Twistlock CVE High golang.org/x/net-v0.0.0-20220624214902-1bab6f366d9e
CVE-2022-41721 Twistlock CVE High golang.org/x/net-v0.0.0-20220624214902-1bab6f366d9e
CVE-2023-28840 Twistlock CVE High github.com/docker/docker-v20.10.17
CVE-2023-28842 Twistlock CVE Medium github.com/docker/docker-v20.10.17
CVE-2023-28841 Twistlock CVE Medium github.com/docker/docker-v20.10.17
CVE-2022-41725 Twistlock CVE High go-1.19.1
CVE-2022-41724 Twistlock CVE High go-1.19.1
CVE-2022-41723 Twistlock CVE High go-1.19.1
CVE-2022-41716 Twistlock CVE High go-1.19.1
CVE-2022-41715 Twistlock CVE High go-1.19.1
CVE-2022-2880 Twistlock CVE High go-1.19.1
CVE-2022-2879 Twistlock CVE High go-1.19.1
CVE-2023-24532 Twistlock CVE Medium go-1.19.1
CVE-2022-41717 Twistlock CVE Medium go-1.19.1
CVE-2023-24537 Twistlock CVE High go-1.19.1
CVE-2023-24538 Twistlock CVE Critical go-1.19.1
CVE-2023-24536 Twistlock CVE High go-1.19.1

VAT: https://vat.dso.mil/vat/image?imageName=tetrate/istio/proxyv2&tag=1.15.1-tetratefips-v1&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/tetrate/istio/1.15/proxyv2/-/jobs/15401640

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 to Open. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add the Approval 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.

Edited by Ghost User
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information