chore(findings): rapidfort/rfpubsub-exe
Summary
rapidfort/rfpubsub-exe has 54 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2024-2961 | Anchore CVE | High | glibc-2.28-236.el8_9.12 |
CVE-2024-2961 | Anchore CVE | High | glibc-devel-2.28-236.el8_9.12 |
CVE-2024-2961 | Anchore CVE | High | glibc-common-2.28-236.el8_9.12 |
CVE-2024-2961 | Anchore CVE | High | glibc-langpack-en-2.28-236.el8_9.12 |
CVE-2020-19190 | Anchore CVE | Low | ncurses-base-6.1-10.20180224.el8 |
CVE-2023-29402 | Anchore CVE | Critical | stdlib-go1.19.3 |
CVE-2020-19187 | Anchore CVE | Low | ncurses-libs-6.1-10.20180224.el8 |
CVE-2020-19185 | Anchore CVE | Low | ncurses-base-6.1-10.20180224.el8 |
CVE-2018-19211 | Anchore CVE | Low | ncurses-libs-6.1-10.20180224.el8 |
CVE-2018-20839 | Anchore CVE | Medium | systemd-239-78.el8 |
CVE-2020-19189 | Anchore CVE | Low | ncurses-libs-6.1-10.20180224.el8 |
CVE-2019-1010022 | Anchore CVE | Critical | glibc-langpack-en-2.28-236.el8_9.12 |
CVE-2023-44487 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2023-29400 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2019-1010022 | Anchore CVE | Critical | glibc-common-2.28-236.el8_9.12 |
CVE-2020-19189 | Anchore CVE | Low | ncurses-base-6.1-10.20180224.el8 |
CVE-2020-19185 | Anchore CVE | Low | ncurses-libs-6.1-10.20180224.el8 |
CVE-2019-1010022 | Anchore CVE | Critical | glibc-2.28-236.el8_9.12 |
CVE-2023-29403 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2023-39318 | Anchore CVE | Medium | stdlib-go1.19.3 |
CVE-2023-29409 | Anchore CVE | Medium | stdlib-go1.19.3 |
CVE-2023-39323 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2020-19187 | Anchore CVE | Low | ncurses-base-6.1-10.20180224.el8 |
CVE-2023-39326 | Anchore CVE | Medium | stdlib-go1.19.3 |
CVE-2023-29405 | Anchore CVE | Critical | stdlib-go1.19.3 |
CVE-2023-24537 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2022-41725 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2018-19217 | Anchore CVE | Low | ncurses-libs-6.1-10.20180224.el8 |
CVE-2023-24532 | Anchore CVE | Medium | stdlib-go1.19.3 |
CVE-2023-24538 | Anchore CVE | Critical | stdlib-go1.19.3 |
CVE-2023-29406 | Anchore CVE | Medium | stdlib-go1.19.3 |
CVE-2023-24534 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2022-41724 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2018-19211 | Anchore CVE | Low | ncurses-base-6.1-10.20180224.el8 |
CVE-2020-19190 | Anchore CVE | Low | ncurses-libs-6.1-10.20180224.el8 |
CVE-2022-41409 | Anchore CVE | Low | pcre2-devel-10.32-3.el8_6 |
CVE-2023-24540 | Anchore CVE | Critical | stdlib-go1.19.3 |
CVE-2022-41409 | Anchore CVE | Low | pcre2-10.32-3.el8_6 |
CVE-2020-19186 | Anchore CVE | Low | ncurses-libs-6.1-10.20180224.el8 |
CVE-2022-41723 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2019-1010022 | Anchore CVE | Critical | glibc-devel-2.28-236.el8_9.12 |
CVE-2018-19217 | Anchore CVE | Low | ncurses-base-6.1-10.20180224.el8 |
CVE-2023-50495 | Anchore CVE | Low | ncurses-libs-6.1-10.20180224.el8 |
CVE-2023-45287 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2023-50495 | Anchore CVE | Low | ncurses-base-6.1-10.20180224.el8 |
CVE-2023-45285 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2022-41717 | Anchore CVE | Medium | stdlib-go1.19.3 |
CVE-2023-29404 | Anchore CVE | Critical | stdlib-go1.19.3 |
CVE-2023-24539 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2020-19186 | Anchore CVE | Low | ncurses-base-6.1-10.20180224.el8 |
CVE-2023-24536 | Anchore CVE | High | stdlib-go1.19.3 |
CVE-2021-3997 | Anchore CVE | Medium | systemd-239-78.el8 |
CVE-2023-39319 | Anchore CVE | Medium | stdlib-go1.19.3 |
CVE-2022-41722 | Anchore CVE | High | stdlib-go1.19.3 |
VAT: https://vat.dso.mil/vat/image?imageName=rapidfort/rfpubsub-exe&tag=1.1.45-rfhardened&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=rapidfort/rfpubsub-exe&tag=1.1.45-rfhardened&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.