chore(findings): loft-sh/vcluster-platform
Summary
loft-sh/vcluster-platform has 108 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=loft-sh/vcluster-platform&tag=4.4.0&branch=master
EPSS (Exploit Prediction Scoring System) provides an estimate of the likelihood that a vulnerability will be exploited in the wild.
KEV (Known Exploited Vulnerabilities) indicates whether a vulnerability is actively being exploited according to CISA.
| id | source | severity | package | impact | workaround | epss_score | kev |
|---|---|---|---|---|---|---|---|
| CVE-2025-47291 | Twistlock CVE | Medium | github.com/containerd/containerd/v2-v2.0.3 | 0.00109 | false | ||
| CVE-2025-47291 | Twistlock CVE | Medium | github.com/containerd/containerd/v2-v2.0.4 | 0.00109 | false | ||
| CVE-2025-58058 | Twistlock CVE | Medium | github.com/ulikunitz/xz-v0.5.12 | 0.00056 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.7 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.3 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.7 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.5 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.3 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.3 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.22.5 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.7 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.7 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.7 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.7 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.2 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.7 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.5 | 0.00053 | false | ||
| CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.11 | 0.00053 | false | ||
| CVE-2025-1767 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.33.1 | 0.00051 | false | ||
| CVE-2025-1767 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.34.0 | 0.00051 | false | ||
| CVE-2025-4563 | Twistlock CVE | Low | k8s.io/kubernetes-v1.33.1 | 0.00032 | false | ||
| CVE-2025-47906 | Twistlock CVE | Low | os/exec-1.24.2 | 0.00022 | false | ||
| CVE-2025-47906 | Twistlock CVE | Low | os/exec-1.23.5 | 0.00022 | false | ||
| CVE-2025-47906 | Twistlock CVE | Low | os/exec-1.24.3 | 0.00022 | false | ||
| CVE-2025-47906 | Twistlock CVE | Low | os/exec-1.24.4 | 0.00022 | false | ||
| CVE-2025-47906 | Twistlock CVE | Low | os/exec-1.23.7 | 0.00022 | false | ||
| CVE-2025-47906 | Twistlock CVE | Low | os/exec-1.24.5 | 0.00022 | false | ||
| CVE-2025-47906 | Twistlock CVE | Low | os/exec-1.22.5 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.24.2 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.24.3 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.11 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.24.4 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.24.3 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.24.3 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.22.5 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.5 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.24.5 | 0.00022 | false | ||
| CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00022 | false | ||
| CVE-2025-5187 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.33.1 | 0.00021 | false | ||
| CVE-2025-4673 | Twistlock CVE | Low | net/http-1.22.5 | 0.00014 | false | ||
| CVE-2025-4673 | Twistlock CVE | Low | net/http-1.24.3 | 0.00014 | false | ||
| CVE-2025-4673 | Twistlock CVE | Low | net/http-1.23.5 | 0.00014 | false | ||
| CVE-2025-4673 | Twistlock CVE | Low | net/http-1.24.2 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.24.3 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.24.2 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.24.3 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.5 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.24.3 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.7 | 0.00014 | false | ||
| CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.22.5 | 0.00014 | false | ||
| CVE-2025-4673 | Twistlock CVE | Low | net/http-1.23.7 | 0.00014 | false | ||
| CVE-2025-22874 | Twistlock CVE | Low | crypto/x509-1.24.3 | 0.00012 | false | ||
| CVE-2025-22874 | Twistlock CVE | Low | crypto/x509-1.24.2 | 0.00012 | false | ||
| CVE-2025-22874 | Anchore CVE | High | stdlib-go1.24.3 | 0.00012 | false | ||
| CVE-2025-22874 | Anchore CVE | High | stdlib-go1.24.3 | 0.00012 | false | ||
| CVE-2025-22874 | Anchore CVE | High | stdlib-go1.24.2 | 0.00012 | false | ||
| CVE-2025-22874 | Anchore CVE | High | stdlib-go1.24.3 | 0.00012 | false | ||
| CVE-2024-7598 | Twistlock CVE | Low | k8s.io/kubernetes-v1.34.0 | 0.00007 | false | ||
| CVE-2024-7598 | Twistlock CVE | Low | k8s.io/kubernetes-v1.33.1 | 0.00007 | false | ||
| CVE-2025-54410 | Twistlock CVE | Low | github.com/docker/docker-v27.1.1 | 0.00006 | false | ||
| CVE-2025-54410 | Twistlock CVE | Low | github.com/docker/docker-v27.5.1 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.7 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.3 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.5 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.3 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.2 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.7 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.7 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.7 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.7 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.7 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.22.5 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.7 | 0.00006 | false | ||
| CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.3 | 0.00006 | false | ||
| GO-2025-3900 | Twistlock CVE | Medium | github.com/go-viper/mapstructure/v2-v2.0.0 | N/A | N/A | ||
| GO-2025-3900 | Twistlock CVE | Medium | github.com/go-viper/mapstructure/v2-v2.2.1 | N/A | N/A | ||
| GO-2025-3787 | Twistlock CVE | Medium | github.com/go-viper/mapstructure/v2-v2.2.1 | N/A | N/A | ||
| GO-2025-3787 | Twistlock CVE | Medium | github.com/go-viper/mapstructure/v2-v2.0.0 | N/A | N/A | ||
| GHSA-jc7w-c686-c4v9 | Anchore CVE | Medium | github.com/ulikunitz/xz-v0.5.12 | N/A | N/A | ||
| GHSA-hj2p-8wj8-pfq4 | Anchore CVE | Low | k8s.io/kubernetes-v1.33.1 | N/A | N/A | ||
| GHSA-fv92-fjc5-jj9h | Anchore CVE | Medium | github.com/go-viper/mapstructure/v2-v2.2.1 | N/A | N/A | ||
| GHSA-fv92-fjc5-jj9h | Anchore CVE | Medium | github.com/go-viper/mapstructure/v2-v2.0.0 | N/A | N/A | ||
| GHSA-cxfp-7pvr-95ff | Anchore CVE | Medium | github.com/containerd/containerd/v2-v2.0.3 | N/A | N/A | ||
| GHSA-cxfp-7pvr-95ff | Anchore CVE | Medium | github.com/containerd/containerd/v2-v2.0.4 | N/A | N/A | ||
| GHSA-82ff-hg59-8x73 | Anchore CVE | Medium | github.com/gorilla/csrf-v1.7.2 | N/A | N/A | ||
| GHSA-82ff-hg59-8x73 | Anchore CVE | Medium | github.com/gorilla/csrf-v1.7.2 | N/A | N/A | ||
| GHSA-6v2p-p543-phr9 | Anchore CVE | High | golang.org/x/oauth2-v0.23.0 | N/A | N/A | ||
| GHSA-4x4m-3c2p-qppc | Anchore CVE | Medium | k8s.io/kubernetes-v1.33.1 | N/A | N/A | ||
| GHSA-4vq8-7jfc-9cvp | Anchore CVE | Low | github.com/docker/docker-v27.5.1+incompatible | N/A | N/A | ||
| GHSA-4vq8-7jfc-9cvp | Anchore CVE | Low | github.com/docker/docker-v27.1.1+incompatible | N/A | N/A | ||
| GHSA-2464-8j7c-4cjm | Anchore CVE | Medium | github.com/go-viper/mapstructure/v2-v2.0.0 | N/A | N/A | ||
| GHSA-2464-8j7c-4cjm | Anchore CVE | Medium | github.com/go-viper/mapstructure/v2-v2.2.1 | N/A | N/A | ||
| CCE-89514-4 | OSCAP Compliance | Medium | N/A | N/A | |||
| CCE-87448-7 | OSCAP Compliance | Medium | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=loft-sh/vcluster-platform&tag=4.4.0&branch=master
Tasks
Contributor:
-
Apply the StatusReview label to this issue for a merge request reviewand wait for feedback
OR
-
Provide justifications for findings in the VAT (docs) -
Apply the StatusVerification label to this issue for a VAT justifications reviewand wait for feedback
Iron Bank:
-
Review findings and justifications
Note: If the above process is rejected for any reason, the
RevieworVerificationlabel will be removed and the issue will be sent back toTo-Do. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theRevieworVerificationlabel.
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 CHORE_TOKEN