chore(findings): opensource/jaegertracing/jaeger-agent (arm64)
Summary
opensource/jaegertracing/jaeger-agent (arm64) has 46 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/jaegertracing/jaeger-agent&tag=1.62.0-arm64&branch=master
id | source | severity | package | impact | workaround |
---|---|---|---|---|---|
CVE-2021-3997 | Anchore CVE | Medium | systemd-libs-252-46.el9_5.2 | ||
CVE-2024-50602 | Anchore CVE | Medium | expat-2.5.0-3.el9_5.1 | ||
CVE-2022-27943 | Anchore CVE | Low | libstdc++-11.5.0-2.el9 | ||
CVE-2022-27943 | Anchore CVE | Low | libgcc-11.5.0-2.el9 | ||
CVE-2024-7264 | Anchore CVE | Low | curl-minimal-7.76.1-31.el9 | ||
CVE-2024-7592 | Anchore CVE | Low | python3-libs-3.9.19-8.el9_5.1 | ||
CVE-2022-41409 | Anchore CVE | Low | pcre2-syntax-10.40-6.el9 | ||
CVE-2021-23336 | Anchore CVE | Medium | python3-3.9.19-8.el9_5.1 | ||
CVE-2024-7264 | Anchore CVE | Low | libcurl-minimal-7.76.1-31.el9 | ||
CVE-2024-11168 | Anchore CVE | Medium | python-unversioned-command-3.9.19-8.el9_5.1 | ||
CVE-2024-11168 | Anchore CVE | Medium | python3-3.9.19-8.el9_5.1 | ||
CVE-2024-11168 | Anchore CVE | Medium | python3-libs-3.9.19-8.el9_5.1 | ||
CVE-2022-41409 | Anchore CVE | Low | pcre2-10.40-6.el9 | ||
CVE-2021-23336 | Anchore CVE | Medium | python-unversioned-command-3.9.19-8.el9_5.1 | ||
CVE-2021-23336 | Anchore CVE | Medium | python3-libs-3.9.19-8.el9_5.1 | ||
CVE-2024-41996 | Anchore CVE | Low | openssl-libs-1:3.2.2-6.el9_5 | ||
CVE-2024-7592 | Anchore CVE | Low | python3-3.9.19-8.el9_5.1 | ||
CVE-2021-3572 | Anchore CVE | Low | python3-pip-wheel-21.3.1-1.el9 | ||
CVE-2024-7592 | Anchore CVE | Low | python-unversioned-command-3.9.19-8.el9_5.1 | ||
CVE-2022-27943 | Anchore CVE | Low | libatomic-11.5.0-2.el9 | ||
CVE-2024-52533 | Twistlock CVE | Medium | glib2-2.68.4-14.el9_4.1 | ||
CVE-2024-9287 | Twistlock CVE | Medium | python3-libs-3.9.19-8.el9_5.1 | ||
CVE-2024-9287 | Twistlock CVE | Medium | python-unversioned-command-3.9.19-8.el9_5.1 | ||
CVE-2024-9287 | Twistlock CVE | Medium | python3-3.9.19-8.el9_5.1 | ||
CVE-2024-50602 | Twistlock CVE | Medium | expat-2.5.0-3.el9_5.1 | ||
CVE-2021-23336 | Twistlock CVE | Medium | python3-libs-3.9.19-8.el9_5.1 | ||
CVE-2021-23336 | Twistlock CVE | Medium | python3-3.9.19-8.el9_5.1 | ||
CVE-2021-23336 | Twistlock CVE | Medium | python-unversioned-command-3.9.19-8.el9_5.1 | ||
CVE-2024-11168 | Twistlock CVE | Medium | python3-libs-3.9.19-8.el9_5.1 | ||
CVE-2024-11168 | Twistlock CVE | Medium | python3-3.9.19-8.el9_5.1 | ||
CVE-2024-11168 | Twistlock CVE | Medium | python-unversioned-command-3.9.19-8.el9_5.1 | ||
CVE-2024-41996 | Twistlock CVE | Low | openssl-libs-3.2.2-6.el9_5 | ||
CVE-2022-27943 | Twistlock CVE | Low | libgcc-11.5.0-2.el9 | ||
CVE-2022-27943 | Twistlock CVE | Low | libatomic-11.5.0-2.el9 | ||
CVE-2022-27943 | Twistlock CVE | Low | libstdc++-11.5.0-2.el9 | ||
CVE-2024-7264 | Twistlock CVE | Low | libcurl-minimal-7.76.1-31.el9 | ||
CVE-2024-7264 | Twistlock CVE | Low | curl-minimal-7.76.1-31.el9 | ||
CVE-2022-41409 | Twistlock CVE | Low | pcre2-syntax-10.40-6.el9 | ||
CVE-2022-41409 | Twistlock CVE | Low | pcre2-10.40-6.el9 | ||
CVE-2024-0397 | Twistlock CVE | Low | python3-libs-3.9.19-8.el9_5.1 | ||
CVE-2024-0397 | Twistlock CVE | Low | python3-3.9.19-8.el9_5.1 | ||
CVE-2024-0397 | Twistlock CVE | Low | python-unversioned-command-3.9.19-8.el9_5.1 | ||
CVE-2024-7592 | Twistlock CVE | Low | python3-3.9.19-8.el9_5.1 | ||
CVE-2024-7592 | Twistlock CVE | Low | python-unversioned-command-3.9.19-8.el9_5.1 | ||
CVE-2024-7592 | Twistlock CVE | Low | python3-libs-3.9.19-8.el9_5.1 | ||
CVE-2021-3572 | Twistlock CVE | Low | python3-pip-wheel-21.3.1-1.el9 |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/jaegertracing/jaeger-agent&tag=1.62.0-arm64&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.