chore(findings): redhat/ubi/ubi9-micro
Summary
redhat/ubi/ubi9-micro has 22 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2024-33602 | Anchore CVE | Low | glibc-2.34-100.el9 |
CVE-2024-33602 | Anchore CVE | Low | glibc-minimal-langpack-2.34-100.el9 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-common-2.34-100.el9 |
CVE-2024-2961 | Anchore CVE | High | glibc-2.34-100.el9 |
CVE-2024-2961 | Anchore CVE | High | glibc-common-2.34-100.el9 |
CVE-2024-33601 | Anchore CVE | Low | glibc-2.34-100.el9 |
CVE-2024-33599 | Anchore CVE | High | glibc-minimal-langpack-2.34-100.el9 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-minimal-langpack-2.34-100.el9 |
CVE-2024-33602 | Anchore CVE | Low | glibc-common-2.34-100.el9 |
CVE-2024-33599 | Anchore CVE | High | glibc-common-2.34-100.el9 |
CVE-2024-2961 | Anchore CVE | High | glibc-minimal-langpack-2.34-100.el9 |
CVE-2024-33601 | Anchore CVE | Low | glibc-common-2.34-100.el9 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-2.34-100.el9 |
CVE-2024-33601 | Anchore CVE | Low | glibc-minimal-langpack-2.34-100.el9 |
CVE-2024-33599 | Anchore CVE | High | glibc-2.34-100.el9 |
CVE-2023-50495 | Anchore CVE | Low | ncurses-libs-6.2-10.20210508.el9 |
CVE-2023-50495 | Anchore CVE | Low | ncurses-base-6.2-10.20210508.el9 |
CVE-2022-27943 | Anchore CVE | Low | libgcc-11.4.1-3.el9 |
CVE-2022-29458 | Anchore CVE | Low | ncurses-base-6.2-10.20210508.el9 |
CVE-2022-41409 | Anchore CVE | Low | pcre2-10.40-5.el9 |
CVE-2022-29458 | Anchore CVE | Low | ncurses-libs-6.2-10.20210508.el9 |
CVE-2022-41409 | Anchore CVE | Low | pcre2-syntax-10.40-5.el9 |
VAT: https://vat.dso.mil/vat/image?imageName=redhat/ubi/ubi9-micro&tag=9.4&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=redhat/ubi/ubi9-micro&tag=9.3&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.