chore(findings): opensource/jekyll/jekyll-builder
Summary
opensource/jekyll/jekyll-builder has 45 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2024-33602 | Anchore CVE | Low | glibc-devel-2.34-83.el9_3.12 |
CVE-2024-26804 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-gconv-extra-2.34-83.el9_3.12 |
CVE-2024-33601 | Anchore CVE | Low | glibc-headers-2.34-83.el9_3.12 |
CVE-2024-33602 | Anchore CVE | Low | glibc-headers-2.34-83.el9_3.12 |
CVE-2024-33599 | Anchore CVE | High | glibc-gconv-extra-2.34-83.el9_3.12 |
CVE-2024-26855 | Anchore CVE | Low | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2024-33599 | Anchore CVE | High | glibc-headers-2.34-83.el9_3.12 |
CVE-2024-33599 | Anchore CVE | High | glibc-devel-2.34-83.el9_3.12 |
CVE-2024-33601 | Anchore CVE | Low | glibc-gconv-extra-2.34-83.el9_3.12 |
CVE-2024-26735 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2024-26801 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2024-33601 | Anchore CVE | Low | glibc-devel-2.34-83.el9_3.12 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-headers-2.34-83.el9_3.12 |
CVE-2024-33602 | Anchore CVE | Low | glibc-gconv-extra-2.34-83.el9_3.12 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-devel-2.34-83.el9_3.12 |
CVE-2022-48644 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48640 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48652 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48658 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2024-26927 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48647 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48662 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48637 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48638 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2024-26828 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2024-26821 | Anchore CVE | Low | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48639 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48635 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48651 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48665 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48666 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48657 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48659 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48646 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48654 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2024-26853 | Anchore CVE | Low | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48650 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48642 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48653 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48660 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48631 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48632 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2022-48648 | Anchore CVE | Medium | kernel-headers-5.14.0-362.24.1.el9_3 |
CVE-2024-26835 | Anchore CVE | Low | kernel-headers-5.14.0-362.24.1.el9_3 |
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.