chore(findings): opensource/argoproj/argocd
Summary
opensource/argoproj/argocd has 17 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
b59c4bf2abe54300ad1cedf436da87a6 | Anchore Compliance | Low | |
57fa9ec087d9e84fa660415015eec945 | Anchore Compliance | Low | |
03b002811f7f1dd314d86fc2cf78088f | Anchore Compliance | Low | |
ec7c2458dcae971eddd19e2b01829d96 | Anchore Compliance | Low | |
9b6af07f2d1d2aff3f91c8a29dbc9c22 | Anchore Compliance | Low | |
GHSA-pxhw-596r-rwq5 | Anchore CVE | Low | k8s.io/kubernetes-v1.26.11 |
GHSA-9m6p-x4h2-6frq | Anchore CVE | Medium | github.com/argoproj/argo-cd/v2-v2.10.7 |
CVE-2023-39322 | Anchore CVE | Medium | git-lfs-3.2.0-2.el9_3 |
CVE-2023-45288 | Twistlock CVE | Critical | git-lfs-3.2.0-2.el9_3 |
CVE-2023-39322 | Twistlock CVE | Medium | git-lfs-3.2.0-2.el9_3 |
CVE-2023-39321 | Twistlock CVE | Medium | git-lfs-3.2.0-2.el9_3 |
CVE-2022-23806 | Twistlock CVE | Medium | git-lfs-3.2.0-2.el9_3 |
CVE-2023-29406 | Twistlock CVE | Medium | git-lfs-3.2.0-2.el9_3 |
CVE-2024-24783 | Twistlock CVE | Medium | git-lfs-3.2.0-2.el9_3 |
CVE-2023-45290 | Twistlock CVE | Medium | git-lfs-3.2.0-2.el9_3 |
CVE-2023-45289 | Twistlock CVE | Medium | git-lfs-3.2.0-2.el9_3 |
CVE-2023-29409 | Twistlock CVE | Medium | git-lfs-3.2.0-2.el9_3 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/argoproj/argocd&tag=v2.10.7&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/argoproj/argocd&tag=v2.10.7&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.