chore(findings): loft-sh/vcluster-pro
Summary
loft-sh/vcluster-pro has 37 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-pro&tag=0.27.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-2024-45338 | Twistlock CVE | High | golang.org/x/net/html-v0.30.0 | 0.00189 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.2 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.2 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.10 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.10 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.2 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.2 | 0.00054 | false | ||
CVE-2025-58058 | Twistlock CVE | Medium | github.com/ulikunitz/xz-v0.5.12 | 0.00051 | false | ||
CVE-2025-1767 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.33.0 | 0.00041 | false | ||
CVE-2025-4563 | Twistlock CVE | Low | k8s.io/kubernetes-v1.33.0 | 0.00028 | false | ||
CVE-2025-5187 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.33.0 | 0.00020 | false | ||
CVE-2025-4673 | Twistlock CVE | Low | net/http-1.24.2 | 0.00019 | false | ||
CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.24.2 | 0.00019 | false | ||
CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.24.2 | 0.00019 | false | ||
CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.24.2 | 0.00019 | false | ||
CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.24.2 | 0.00019 | false | ||
CVE-2025-22870 | Twistlock CVE | Medium | golang.org/x/net/proxy-v0.30.0 | 0.00015 | false | ||
CVE-2025-54410 | Twistlock CVE | Low | github.com/docker/docker-v25.0.6 | 0.00014 | false | ||
CVE-2025-22874 | Twistlock CVE | Low | crypto/x509-1.24.2 | 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.2 | 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.2 | 0.00012 | false | ||
CVE-2024-7598 | Twistlock CVE | Low | k8s.io/kubernetes-v1.33.0 | 0.00007 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.2 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.10 | 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.10 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.2 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.2 | 0.00006 | false | ||
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.0 | N/A | N/A | ||
GHSA-6v2p-p543-phr9 | Anchore CVE | High | golang.org/x/oauth2-v0.23.0 | N/A | N/A | ||
GHSA-6v2p-p543-phr9 | Anchore CVE | High | golang.org/x/oauth2-v0.23.0 | 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.0 | N/A | N/A | ||
GHSA-4vq8-7jfc-9cvp | Anchore CVE | Low | github.com/docker/docker-v25.0.6+incompatible | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=loft-sh/vcluster-pro&tag=0.27.0&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.