chore(findings): rancher-federal/rke2/hardened-dns-node-cache
Summary
rancher-federal/rke2/hardened-dns-node-cache has 20 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-qc2g-gmh6-95p4 | Anchore CVE | Medium | k8s.io/kubernetes-v1.24.10 |
GHSA-cgcv-5272-97pr | Anchore CVE | Medium | k8s.io/kubernetes-v1.24.10 |
GHSA-f9jg-8p32-2f55 | Anchore CVE | Low | k8s.io/kubernetes-v1.24.10 |
GHSA-4374-p667-p6c8 | Anchore CVE | Medium | golang.org/x/net-v0.7.0 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.7.0 |
CVE-2023-4813 | OSCAP Compliance | Medium | |
CVE-2023-4039 | OSCAP Compliance | Medium | |
CVE-2023-2728 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.24.10 |
CVE-2023-2727 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.24.10 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.20.3 |
CVE-2021-25743 | Twistlock CVE | Low | k8s.io/kubernetes-v1.24.10 |
CVE-2023-4813 | Twistlock CVE | Medium | glibc-2.31-150300.58.1 |
CVE-2023-3978 | Twistlock CVE | Medium | golang.org/x/net-v0.7.0 |
CVE-2023-39325 | Twistlock CVE | Medium | golang.org/x/net-v0.7.0 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.21.1 |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.20.3 |
CVE-2023-44487 | Twistlock CVE | Medium | golang.org/x/net-v0.7.0 |
VAT: https://vat.dso.mil/vat/image?imageName=rancher-federal/rke2/hardened-dns-node-cache&tag=1.22.20-build20230406&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=rancher-federal/rke2/hardened-dns-node-cache&tag=1.22.20-build20230406&branch=master
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.