chore(findings): redhat/ubi/ubi7
Summary
redhat/ubi/ubi7 has 75 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2023-28320 | Anchore CVE | Low | curl-7.29.0-59.el7_9.1 |
CVE-2023-28322 | Anchore CVE | Low | curl-7.29.0-59.el7_9.1 |
CVE-2023-28322 | Anchore CVE | Low | libcurl-7.29.0-59.el7_9.1 |
CVE-2023-28320 | Anchore CVE | Low | libcurl-7.29.0-59.el7_9.1 |
CVE-2023-4156 | Anchore CVE | Low | gawk-4.0.2-4.el7_3.1 |
CVE-2014-3566 | Anchore CVE | High | nss-3.79.0-5.el7_9 |
CVE-2014-3566 | Anchore CVE | High | nss-tools-3.79.0-5.el7_9 |
CVE-2014-3566 | Anchore CVE | High | nss-sysinit-3.79.0-5.el7_9 |
CCE-27157-7 | OSCAP Compliance | High | |
CVE-2021-33294 | Twistlock CVE | Low | elfutils-default-yama-scope-0.176-5.el7 |
CVE-2021-33294 | Twistlock CVE | Low | elfutils-libs-0.176-5.el7 |
CVE-2021-33294 | Twistlock CVE | Low | elfutils-libelf-0.176-5.el7 |
CVE-2022-48065 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-48065 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-48064 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-48064 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-48063 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-48063 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-35205 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-35205 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2020-21490 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2020-21490 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2020-19726 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2020-19726 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2020-19724 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2020-19724 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-47696 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-47696 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-47695 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-47695 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-47673 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-47673 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-47011 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-47011 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-47010 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-47010 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-47008 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-47008 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-47007 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-47007 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-45703 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-45703 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-44840 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2022-44840 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-35206 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2022-35206 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2021-46174 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2021-46174 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2020-35342 | Twistlock CVE | Low | gdb-gdbserver-7.6.1-120.el7 |
CVE-2020-35342 | Twistlock CVE | Low | binutils-2.27-44.base.el7_9.1 |
CVE-2020-19190 | Twistlock CVE | Medium | ncurses-5.9-14.20130511.el7_4 |
CVE-2020-19190 | Twistlock CVE | Medium | ncurses-libs-5.9-14.20130511.el7_4 |
CVE-2020-19190 | Twistlock CVE | Medium | ncurses-base-5.9-14.20130511.el7_4 |
CVE-2020-19189 | Twistlock CVE | Medium | ncurses-base-5.9-14.20130511.el7_4 |
CVE-2020-19189 | Twistlock CVE | Medium | ncurses-libs-5.9-14.20130511.el7_4 |
CVE-2020-19189 | Twistlock CVE | Medium | ncurses-5.9-14.20130511.el7_4 |
CVE-2020-19188 | Twistlock CVE | Medium | ncurses-libs-5.9-14.20130511.el7_4 |
CVE-2020-19188 | Twistlock CVE | Medium | ncurses-5.9-14.20130511.el7_4 |
CVE-2020-19188 | Twistlock CVE | Medium | ncurses-base-5.9-14.20130511.el7_4 |
CVE-2020-19187 | Twistlock CVE | Medium | ncurses-5.9-14.20130511.el7_4 |
CVE-2020-19187 | Twistlock CVE | Medium | ncurses-libs-5.9-14.20130511.el7_4 |
CVE-2020-19187 | Twistlock CVE | Medium | ncurses-base-5.9-14.20130511.el7_4 |
CVE-2020-19186 | Twistlock CVE | Medium | ncurses-libs-5.9-14.20130511.el7_4 |
CVE-2020-19186 | Twistlock CVE | Medium | ncurses-5.9-14.20130511.el7_4 |
CVE-2020-19186 | Twistlock CVE | Medium | ncurses-base-5.9-14.20130511.el7_4 |
CVE-2020-19185 | Twistlock CVE | Medium | ncurses-5.9-14.20130511.el7_4 |
CVE-2020-19185 | Twistlock CVE | Medium | ncurses-libs-5.9-14.20130511.el7_4 |
CVE-2020-19185 | Twistlock CVE | Medium | ncurses-base-5.9-14.20130511.el7_4 |
CVE-2020-22916 | Twistlock CVE | Low | xz-5.2.2-2.el7_9 |
CVE-2020-22916 | Twistlock CVE | Low | xz-libs-5.2.2-2.el7_9 |
CVE-2020-22218 | Twistlock CVE | Medium | libssh2-1.8.0-4.el7 |
CVE-2022-48554 | Twistlock CVE | Low | file-libs-5.11-37.el7 |
CVE-2023-4641 | Twistlock CVE | Low | shadow-utils-4.6-5.el7 |
CVE-2015-1283 | Twistlock CVE | Medium | python-2.7.5 |
CVE-2015-1283 | Twistlock CVE | Medium | python-2.7.5 |
VAT: https://vat.dso.mil/vat/image?imageName=redhat/ubi/ubi7&tag=7.9&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=redhat/ubi/ubi7&tag=7.9&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.