chore(findings): opensource/ceph/ceph
Summary
opensource/ceph/ceph has 144 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2015-20107 | Twistlock CVE | Medium | python36-3.6.8-38.module+el8.5.0+12207+5c5719bc |
CVE-2022-30635 | Twistlock CVE | Medium | containernetworking-plugins-1.1.1-3.module+el8.7.0+17064+3b31f55c |
CVE-2022-30633 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-30632 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-30631 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-30630 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-2880 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-2880 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-2880 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-2880 | Twistlock CVE | Medium | conmon-2.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2022-2879 | Twistlock CVE | Medium | conmon-2.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2022-2879 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-2879 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-2879 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-27664 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-27664 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-27664 | Twistlock CVE | Medium | containernetworking-plugins-1.1.1-3.module+el8.7.0+17064+3b31f55c |
CVE-2022-27664 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-27664 | Twistlock CVE | Medium | conmon-2.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2021-38561 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2021-38561 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2021-33198 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2020-8945 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2020-8945 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2020-8945 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2020-28362 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2020-28362 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2020-28362 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2020-14040 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-28131 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2021-20206 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2021-20206 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2021-20206 | Twistlock CVE | Medium | containernetworking-plugins-1.1.1-3.module+el8.7.0+17064+3b31f55c |
CVE-2022-1705 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2021-34558 | Twistlock CVE | Medium | runc-1.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2021-34558 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2021-34558 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2021-34558 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2021-3114 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2020-10756 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2018-20839 | Twistlock CVE | Medium | systemd-udev-239-68.el8 |
CVE-2022-41715 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-41715 | Twistlock CVE | Medium | containernetworking-plugins-1.1.1-3.module+el8.7.0+17064+3b31f55c |
CVE-2022-41715 | Twistlock CVE | Medium | conmon-2.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2022-41715 | Twistlock CVE | Medium | runc-1.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2022-41715 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-41715 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2020-10749 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2021-20199 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-3821 | Twistlock CVE | Medium | systemd-udev-239-68.el8 |
CVE-2022-1962 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-32148 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2020-14370 | Twistlock CVE | Medium | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2021-4024 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2021-4024 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-3235 | Twistlock CVE | Low | vim-minimal-8.0.1763-19.el8_6.4 |
CVE-2022-32189 | Twistlock CVE | Low | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-32189 | Twistlock CVE | Low | containernetworking-plugins-1.1.1-3.module+el8.7.0+17064+3b31f55c |
CVE-2022-32189 | Twistlock CVE | Low | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-32189 | Twistlock CVE | Low | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-32189 | Twistlock CVE | Low | runc-1.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2022-32189 | Twistlock CVE | Low | conmon-2.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2020-29652 | Twistlock CVE | Low | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2021-3997 | Twistlock CVE | Low | systemd-udev-239-68.el8 |
CVE-2021-43784 | Twistlock CVE | Low | runc-1.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2022-3705 | Twistlock CVE | Low | vim-minimal-8.0.1763-19.el8_6.4 |
CVE-2022-3352 | Twistlock CVE | Low | vim-minimal-8.0.1763-19.el8_6.4 |
CVE-2021-3595 | Twistlock CVE | Low | libslirp-4.4.0-1.module+el8.7.0+17064+3b31f55c |
CVE-2021-3594 | Twistlock CVE | Low | libslirp-4.4.0-1.module+el8.7.0+17064+3b31f55c |
CVE-2021-3593 | Twistlock CVE | Low | libslirp-4.4.0-1.module+el8.7.0+17064+3b31f55c |
CVE-2021-3592 | Twistlock CVE | Low | libslirp-4.4.0-1.module+el8.7.0+17064+3b31f55c |
CVE-2020-1702 | Twistlock CVE | Low | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-33070 | Twistlock CVE | Low | protobuf-c-1.3.0-6.el8 |
CVE-2022-30629 | Twistlock CVE | Low | conmon-2.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2022-30629 | Twistlock CVE | Low | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-30629 | Twistlock CVE | Low | runc-1.1.4-1.module+el8.7.0+17064+3b31f55c |
CVE-2022-30629 | Twistlock CVE | Low | containers-common-1-43.module+el8.7.0+17064+3b31f55c |
CVE-2022-30629 | Twistlock CVE | Low | containernetworking-plugins-1.1.1-3.module+el8.7.0+17064+3b31f55c |
CVE-2022-30629 | Twistlock CVE | Low | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-3821 | Anchore CVE | Medium | systemd-udev-239-68.el8 |
CVE-2022-3235 | Anchore CVE | Low | vim-minimal-2:8.0.1763-19.el8_6.4 |
CVE-2022-33070 | Anchore CVE | Low | protobuf-c-1.3.0-6.el8 |
CVE-2022-3705 | Anchore CVE | Low | vim-minimal-2:8.0.1763-19.el8_6.4 |
f661596ecf0df8261cbb94fd721adc6e | Anchore Compliance | Critical | |
cbff271f45d32e78dcc1979dbca9c14d | Anchore Compliance | Critical | |
CVE-2022-45061 | Twistlock CVE | Medium | python36-3.6.8-38.module+el8.5.0+12207+5c5719bc |
CVE-2022-29217 | Twistlock CVE | Medium | python3-jwt-1.6.1-2.el8 |
CVE-2022-29217 | Anchore CVE | Medium | python3-jwt-1.6.1-2.el8 |
CVE-2022-4122 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-4122 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-4123 | Twistlock CVE | Low | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-4123 | Twistlock CVE | Low | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-3352 | Anchore CVE | Low | vim-minimal-2:8.0.1763-19.el8_6.4 |
CVE-2022-45873 | Twistlock CVE | Medium | systemd-udev-239-68.el8 |
CVE-2022-4141 | Twistlock CVE | Low | vim-minimal-8.0.1763-19.el8_6.4 |
CVE-2022-32149 | Twistlock CVE | Medium | podman-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-32149 | Twistlock CVE | Medium | podman-catatonit-4.2.0-4.module+el8.7.0+17064+3b31f55c |
CVE-2022-4292 | Twistlock CVE | Low | vim-minimal-8.0.1763-19.el8_6.4 |
CVE-2022-4293 | Twistlock CVE | Low | vim-minimal-8.0.1763-19.el8_6.4 |
CVE-2022-3491 | Twistlock CVE | Low | vim-minimal-8.0.1763-19.el8_6.4 |
CVE-2022-3650 | Twistlock CVE | Critical | libcephfs2-17.2.5-0.el8 |
CVE-2022-3650 | Twistlock CVE | Critical | librados2-17.2.5-0.el8 |
CVE-2022-3650 | Twistlock CVE | Critical | libradosstriper1-17.2.5-0.el8 |
CVE-2022-3650 | Twistlock CVE | Critical | librbd1-17.2.5-0.el8 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.18.7 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/ceph/ceph&tag=v17.2.5&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/opensource/ceph/ceph/-/jobs/15882628
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Hardening::Approval" label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications -
Send approval request to Authorizing Official -
Close issue after approval from Authorizing Official
Note: If the above approval process is rejected for any reason, the
Approval
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 theApproval
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.