chore(findings): opensource/jekyll/jekyll-builder
Summary
opensource/jekyll/jekyll-builder has 193 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2021-3826 | Anchore CVE | Low | binutils-2.35.2-43.el9 |
CVE-2024-22195 | Anchore CVE | Medium | rust-srpm-macros-17-4.el9 |
CVE-2021-3997 | Anchore CVE | Medium | systemd-252-32.el9_4 |
CVE-2023-1579 | Anchore CVE | Medium | binutils-2.35.2-43.el9 |
CVE-2024-2961 | Anchore CVE | High | glibc-gconv-extra-2.34-100.el9 |
CVE-2016-20012 | Anchore CVE | Low | openssh-clients-8.7p1-38.el9 |
CVE-2005-2541 | Anchore CVE | Medium | tar-2:1.34-6.el9_1 |
CVE-2023-24056 | Anchore CVE | Low | libpkgconf-1.7.3-10.el9 |
CVE-2022-27943 | Anchore CVE | Low | gcc-11.4.1-3.el9 |
CVE-2024-25260 | Anchore CVE | Low | elfutils-default-yama-scope-0.190-2.el9 |
CVE-2021-32256 | Anchore CVE | Medium | binutils-2.35.2-43.el9 |
CVE-2024-2961 | Anchore CVE | High | glibc-devel-2.34-100.el9 |
CVE-2023-24056 | Anchore CVE | Low | pkgconf-m4-1.7.3-10.el9 |
CVE-2022-27943 | Anchore CVE | Low | libstdc++-devel-11.4.1-3.el9 |
CVE-2024-25260 | Anchore CVE | Low | elfutils-0.190-2.el9 |
CVE-2024-33602 | Anchore CVE | Low | glibc-devel-2.34-100.el9 |
CVE-2022-4899 | Anchore CVE | Low | zstd-1.5.1-2.el9 |
CVE-2021-3997 | Anchore CVE | Medium | systemd-rpm-macros-252-32.el9_4 |
CVE-2024-33601 | Anchore CVE | Low | glibc-gconv-extra-2.34-100.el9 |
CVE-2022-27943 | Anchore CVE | Low | cpp-11.4.1-3.el9 |
CVE-2024-2961 | Anchore CVE | High | glibc-headers-2.34-100.el9 |
CVE-2016-20012 | Anchore CVE | Low | openssh-8.7p1-38.el9 |
CVE-2022-38533 | Anchore CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2021-45261 | Anchore CVE | Low | patch-2.7.6-16.el9 |
CVE-2022-27943 | Anchore CVE | Low | gcc-plugin-annobin-11.4.1-3.el9 |
CVE-2024-33599 | Anchore CVE | High | glibc-devel-2.34-100.el9 |
CVE-2022-38533 | Anchore CVE | Low | binutils-2.35.2-43.el9 |
CVE-2024-33599 | Anchore CVE | High | glibc-gconv-extra-2.34-100.el9 |
CVE-2022-27943 | Anchore CVE | Low | gcc-gfortran-11.4.1-3.el9 |
CVE-2023-24056 | Anchore CVE | Low | pkgconf-pkg-config-1.7.3-10.el9 |
CVE-2022-27943 | Anchore CVE | Low | libgomp-11.4.1-3.el9 |
CVE-2024-33602 | Anchore CVE | Low | glibc-headers-2.34-100.el9 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-devel-2.34-100.el9 |
CVE-2022-27943 | Anchore CVE | Low | libgfortran-11.4.1-3.el9 |
CVE-2024-33599 | Anchore CVE | High | glibc-headers-2.34-100.el9 |
CVE-2022-27943 | Anchore CVE | Low | libquadmath-11.4.1-3.el9 |
CVE-2023-1972 | Anchore CVE | Low | binutils-2.35.2-43.el9 |
CVE-2022-29458 | Anchore CVE | Low | ncurses-6.2-10.20210508.el9 |
CVE-2021-45078 | Anchore CVE | Medium | binutils-2.35.2-43.el9 |
CVE-2024-2511 | Anchore CVE | Low | openssl-1:3.0.7-27.el9 |
CVE-2024-33601 | Anchore CVE | Low | glibc-headers-2.34-100.el9 |
CVE-2021-32256 | Anchore CVE | Medium | binutils-gold-2.35.2-43.el9 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-gconv-extra-2.34-100.el9 |
CVE-2022-0529 | Anchore CVE | Low | unzip-6.0-56.el9 |
CVE-2023-1579 | Anchore CVE | Medium | binutils-gold-2.35.2-43.el9 |
CVE-2022-0530 | Anchore CVE | Low | unzip-6.0-56.el9 |
CVE-2024-33601 | Anchore CVE | Low | glibc-devel-2.34-100.el9 |
CVE-2024-25260 | Anchore CVE | Low | elfutils-libelf-0.190-2.el9 |
CVE-2023-39804 | Anchore CVE | Low | tar-2:1.34-6.el9_1 |
CVE-2022-27943 | Anchore CVE | Low | gcc-c++-11.4.1-3.el9 |
CVE-2022-27943 | Anchore CVE | Low | libquadmath-devel-11.4.1-3.el9 |
CVE-2024-25260 | Anchore CVE | Low | elfutils-debuginfod-client-0.190-2.el9 |
CVE-2024-33602 | Anchore CVE | Low | glibc-gconv-extra-2.34-100.el9 |
CVE-2021-3826 | Anchore CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2015-1197 | Anchore CVE | Low | cpio-2.13-16.el9 |
CVE-2024-25260 | Anchore CVE | Low | elfutils-libs-0.190-2.el9 |
CVE-2023-1972 | Anchore CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-headers-2.34-100.el9 |
CVE-2021-45078 | Anchore CVE | Medium | binutils-gold-2.35.2-43.el9 |
CVE-2023-7207 | Anchore CVE | Medium | cpio-2.13-16.el9 |
CVE-2023-24056 | Anchore CVE | Low | pkgconf-1.7.3-10.el9 |
CVE-2021-3997 | Anchore CVE | Medium | systemd-pam-252-32.el9_4 |
CVE-2021-4204 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2019-16089 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-52478 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-3903 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-34866 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26928 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-0564 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-28713 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26687 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-2961 | Twistlock CVE | Critical | glibc-headers-2.34-100.el9 |
CVE-2024-2961 | Twistlock CVE | Critical | glibc-gconv-extra-2.34-100.el9 |
CVE-2024-2961 | Twistlock CVE | Critical | glibc-devel-2.34-100.el9 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-headers-2.34-100.el9 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-devel-2.34-100.el9 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-gconv-extra-2.34-100.el9 |
CVE-2021-45078 | Twistlock CVE | Medium | binutils-gold-2.35.2-43.el9 |
CVE-2021-45078 | Twistlock CVE | Medium | binutils-2.35.2-43.el9 |
CVE-2023-51767 | Twistlock CVE | Medium | openssh-8.7p1-38.el9 |
CVE-2023-51767 | Twistlock CVE | Medium | openssh-clients-8.7p1-38.el9 |
CVE-2023-1579 | Twistlock CVE | Medium | binutils-2.35.2-43.el9 |
CVE-2023-1579 | Twistlock CVE | Medium | binutils-gold-2.35.2-43.el9 |
CVE-2021-3997 | Twistlock CVE | Medium | systemd-rpm-macros-252-32.el9_4 |
CVE-2021-3997 | Twistlock CVE | Medium | systemd-pam-252-32.el9_4 |
CVE-2021-3997 | Twistlock CVE | Medium | systemd-252-32.el9_4 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-devel-2.34-100.el9 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-headers-2.34-100.el9 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-gconv-extra-2.34-100.el9 |
CVE-2021-20197 | Twistlock CVE | Medium | binutils-2.35.2-43.el9 |
CVE-2021-20197 | Twistlock CVE | Medium | binutils-gold-2.35.2-43.el9 |
CVE-2022-44840 | Twistlock CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2022-44840 | Twistlock CVE | Low | binutils-2.35.2-43.el9 |
CVE-2021-3826 | Twistlock CVE | Low | binutils-2.35.2-43.el9 |
CVE-2021-3826 | Twistlock CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2022-47011 | Twistlock CVE | Low | gdb-minimal-10.2-13.el9 |
CVE-2022-47011 | Twistlock CVE | Low | binutils-2.35.2-43.el9 |
CVE-2022-47011 | Twistlock CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2022-47010 | Twistlock CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2022-47010 | Twistlock CVE | Low | gdb-minimal-10.2-13.el9 |
CVE-2022-47010 | Twistlock CVE | Low | binutils-2.35.2-43.el9 |
CVE-2022-47008 | Twistlock CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2022-47008 | Twistlock CVE | Low | binutils-2.35.2-43.el9 |
CVE-2022-47007 | Twistlock CVE | Low | binutils-2.35.2-43.el9 |
CVE-2022-47007 | Twistlock CVE | Low | gdb-minimal-10.2-13.el9 |
CVE-2022-47007 | Twistlock CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2022-38533 | Twistlock CVE | Low | binutils-2.35.2-43.el9 |
CVE-2022-38533 | Twistlock CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-devel-2.34-100.el9 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-headers-2.34-100.el9 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-gconv-extra-2.34-100.el9 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-gconv-extra-2.34-100.el9 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-headers-2.34-100.el9 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-devel-2.34-100.el9 |
CVE-2024-2511 | Twistlock CVE | Low | openssl-3.0.7-27.el9 |
CVE-2023-1972 | Twistlock CVE | Low | binutils-2.35.2-43.el9 |
CVE-2023-1972 | Twistlock CVE | Low | binutils-gold-2.35.2-43.el9 |
CVE-2024-34064 | Twistlock CVE | Medium | rust-srpm-macros-17-4.el9 |
CVE-2023-7042 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-52452 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-42739 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2020-14304 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-3534 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-3542 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-0045 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-3424 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-23222 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2020-13844 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-2905 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-3633 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-3606 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-24959 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-52447 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-28712 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-37454 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-47233 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-25265 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-28711 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26810 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-45402 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-20320 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-3344 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-1118 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-4202 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-3714 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-3629 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26812 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-26966 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-52568 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-52481 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-0500 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2021-47041 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26695 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-0775 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-1247 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26878 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48696 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48689 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48688 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-27056 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48690 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26925 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26882 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26889 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48687 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26861 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48697 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26962 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26974 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26945 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-27030 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48673 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26953 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26880 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48705 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26979 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26950 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26915 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26865 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48702 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-27043 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48695 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-27038 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26868 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26883 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48675 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26923 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26951 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2022-48704 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26851 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-26684 | Anchore CVE | Low | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2024-27050 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
CVE-2023-52462 | Anchore CVE | Medium | kernel-headers-5.14.0-427.16.1.el9_4 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/jekyll/jekyll-builder&tag=4.3.3&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/jekyll/jekyll-builder&tag=4.3.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.