chore(findings): opensource/mysql/mysql8
Summary
opensource/mysql/mysql8 has 68 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2022-48695 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26878 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26684 | Anchore CVE | Low | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26974 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26880 | Anchore CVE | Low | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-27056 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2023-52462 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26889 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26865 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26915 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-27038 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26945 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26951 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26868 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48702 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26851 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26883 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48697 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48688 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48696 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26979 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26882 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-27043 | Anchore CVE | Low | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26861 | Anchore CVE | Low | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48675 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48705 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48704 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48689 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26962 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48690 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48687 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2022-48673 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26923 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-27050 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-27030 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26950 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26925 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-26953 | Anchore CVE | Medium | kernel-headers-5.14.0-427.18.1.el9_4 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-33601 | Anchore CVE | Low | glibc-devel-2.34-100.el9_4.2 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-33599 | Anchore CVE | High | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-2961 | Anchore CVE | High | glibc-devel-2.34-100.el9_4.2 |
CVE-2024-33602 | Anchore CVE | Low | glibc-devel-2.34-100.el9_4.2 |
CVE-2024-33599 | Anchore CVE | High | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-2961 | Anchore CVE | High | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-33601 | Anchore CVE | Low | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-33601 | Anchore CVE | Low | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-33602 | Anchore CVE | Low | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-33599 | Anchore CVE | High | glibc-devel-2.34-100.el9_4.2 |
CVE-2024-2961 | Anchore CVE | High | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-33600 | Anchore CVE | Medium | glibc-devel-2.34-100.el9_4.2 |
CVE-2024-33602 | Anchore CVE | Low | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-2961 | Twistlock CVE | Critical | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-2961 | Twistlock CVE | Critical | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-2961 | Twistlock CVE | Critical | glibc-devel-2.34-100.el9_4.2 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-devel-2.34-100.el9_4.2 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-devel-2.34-100.el9_4.2 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-devel-2.34-100.el9_4.2 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-gconv-extra-2.34-100.el9_4.2 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-headers-2.34-100.el9_4.2 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-devel-2.34-100.el9_4.2 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/mysql/mysql8&tag=8.0.36-ubi9&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/mysql/mysql8&tag=8.0.36-ubi9&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.