chore(findings): opensource/loft-sh/vcluster
Summary
opensource/loft-sh/vcluster has 14 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-xw73-rw38-6vjc | Anchore CVE | Medium | github.com/docker/docker-v24.0.7+incompatible |
GHSA-7ww5-4wqc-m92c | Anchore CVE | Medium | github.com/containerd/containerd-v1.7.6 |
GHSA-45x7-px36-x8w8 | Anchore CVE | Medium | golang.org/x/crypto-v0.14.0 |
GHSA-8r3f-844c-mc37 | Anchore CVE | Medium | google.golang.org/protobuf-v1.31.0 |
GHSA-8pgv-569h-w5rw | Anchore CVE | High | go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc-v0.25.0 |
GHSA-8r3f-844c-mc37 | Anchore CVE | Medium | google.golang.org/protobuf-v1.30.0 |
GHSA-8r3f-844c-mc37 | Anchore CVE | Medium | google.golang.org/protobuf-v1.32.0 |
GHSA-xw73-rw38-6vjc | Anchore CVE | Medium | github.com/docker/docker-v24.0.7+incompatible |
CVE-2023-47108 | Twistlock CVE | High | go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc-v0.25.0 |
CVE-2024-24557 | Twistlock CVE | Medium | github.com/docker/docker-v24.0.7 |
PRISMA-2023-0056 | Twistlock CVE | Medium | github.com/sirupsen/logrus-v1.9.0 |
CVE-2023-45288 | Twistlock CVE | Medium | golang.org/x/net/http2-v0.17.0 |
CVE-2023-45288 | Twistlock CVE | Medium | golang.org/x/net/http2-v0.21.0 |
CVE-2023-45288 | Twistlock CVE | Medium | golang.org/x/net/http2-v0.20.0 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/loft-sh/vcluster&tag=v0.19.5&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/loft-sh/vcluster&tag=v0.19.5&branch=master
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the StatusVerification 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.