chore(findings): rancher-federal/rke2/rke2-runtime
Summary
rancher-federal/rke2/rke2-runtime has 120 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-xc8m-28vv-4pjc | Anchore CVE | Medium | k8s.io/kubernetes-v1.26.0 |
GHSA-qc2g-gmh6-95p4 | Anchore CVE | Medium | k8s.io/kubernetes-v1.26.0 |
GHSA-cgcv-5272-97pr | Anchore CVE | Medium | k8s.io/kubernetes-v1.26.0 |
GHSA-6xv5-86q9-7xr8 | Anchore CVE | Medium | github.com/cyphar/filepath-securejoin-v0.2.3 |
GHSA-6xv5-86q9-7xr8 | Anchore CVE | Medium | github.com/cyphar/filepath-securejoin-v0.2.3 |
GHSA-f9jg-8p32-2f55 | Anchore CVE | Low | k8s.io/kubernetes-v1.26.0 |
GHSA-4374-p667-p6c8 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-4374-p667-p6c8 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-4374-p667-p6c8 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-4374-p667-p6c8 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-4374-p667-p6c8 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-4374-p667-p6c8 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-4374-p667-p6c8 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.8.0 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.19.5 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.19.9 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.19.9 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.19.9 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.19.9 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.19.5 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.19.9 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.19.9 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.19.5 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-29403 | Twistlock CVE | High | go-1.19.5 |
CVE-2023-29403 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-29403 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-29403 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-29403 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-29403 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-29403 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-29403 | Twistlock CVE | High | go-1.19.9 |
CVE-2023-29403 | Twistlock CVE | High | go-1.19.9 |
CVE-2023-2431 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.26.0 |
CVE-2023-2727 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.26.0 |
CVE-2023-2728 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.26.0 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.19.9 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.19.9 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.19.5 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.19.9 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.19.9 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.19.5 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39533 | Twistlock CVE | High | go-1.19.5 |
CVE-2023-39533 | Twistlock CVE | High | go-1.19.9 |
CVE-2023-39533 | Twistlock CVE | High | go-1.19.9 |
CVE-2023-39533 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-39533 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-39533 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-39533 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-39533 | Twistlock CVE | High | go-1.20.3 |
CVE-2023-39533 | Twistlock CVE | High | go-1.20.3 |
GHSA-6xv5-86q9-7xr8 | Twistlock CVE | Medium | github.com/cyphar/filepath-securejoin-v0.2.3 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.19.5 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.19.9 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.19.9 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.19.9 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.19.9 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.19.5 |
CVE-2023-3978 | Twistlock CVE | Medium | golang.org/x/net-v0.8.0 |
CVE-2023-39325 | Twistlock CVE | Medium | golang.org/x/net-v0.8.0 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.19.9 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.19.9 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.19.5 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-45142 | Twistlock CVE | High | go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful-v0.20.0 |
CVE-2023-45142 | Twistlock CVE | High | go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp-v0.20.0 |
CVE-2023-45142 | Twistlock CVE | High | go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp-v0.35.0 |
CVE-2023-44487 | Twistlock CVE | Medium | golang.org/x/net-v0.8.0 |
VAT: https://vat.dso.mil/vat/image?imageName=rancher-federal/rke2/rke2-runtime&tag=v1.25.10-rke2r1&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/rancher-federal/rke2/rke2-runtime/-/jobs/22903090
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Hardening::Verification" 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.