chore(findings): opensource/apache/solr-9
Summary
opensource/apache/solr-9 has 79 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2024-23226 | Anchore CVE | High | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2023-42956 | Anchore CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2024-23252 | Anchore CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2021-3997 | Anchore CVE | Medium | systemd-rpm-macros-252-32.el9_4 |
CVE-2024-2511 | Anchore CVE | Low | openssl-1:3.0.7-27.el9 |
CVE-2023-42843 | Anchore CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2021-3997 | Anchore CVE | Medium | systemd-pam-252-32.el9_4 |
CVE-2023-42950 | Anchore CVE | High | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2024-23280 | Anchore CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2024-23263 | Anchore CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2021-3997 | Anchore CVE | Medium | systemd-252-32.el9_4 |
CVE-2024-23254 | Anchore CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2021-3997 | Anchore CVE | Medium | systemd-udev-252-32.el9_4 |
CVE-2024-23284 | Anchore CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2022-30294 | Anchore CVE | Low | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2024-25260 | Anchore CVE | Low | elfutils-libelf-0.190-2.el9 |
CVE-2020-27216 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2020-12413 | Anchore CVE | Low | nss-sysinit-3.90.0-7.el9_4 |
CVE-2017-7656 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2009-5046 | Anchore CVE | Medium | servlet-api-4.0.6 |
CVE-2021-31535 | Anchore CVE | High | libX11-1.7.0-9.el9 |
CVE-2021-28169 | Anchore CVE | Medium | servlet-api-4.0.6 |
CVE-2022-3857 | Anchore CVE | Low | libpng-2:1.6.37-12.el9 |
CVE-2009-5045 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2024-25260 | Anchore CVE | Low | elfutils-default-yama-scope-0.190-2.el9 |
CVE-2021-34428 | Anchore CVE | Low | servlet-api-4.0.6 |
CVE-2022-2047 | Anchore CVE | Low | servlet-api-4.0.6 |
CVE-2023-44487 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2022-27943 | Anchore CVE | Low | libatomic-11.4.1-3.el9 |
CVE-2022-3857 | Anchore CVE | Low | java-17-openjdk-1:17.0.11.0.9-2.el9 |
CVE-2021-3782 | Anchore CVE | Medium | libwayland-egl-1.21.0-1.el9 |
CVE-2023-26049 | Anchore CVE | Medium | servlet-api-4.0.6 |
CVE-2022-2048 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2021-31535 | Anchore CVE | High | libX11-common-1.7.0-9.el9 |
CVE-2022-3554 | Anchore CVE | Medium | libX11-xcb-1.7.0-9.el9 |
CVE-2023-1916 | Anchore CVE | Low | libtiff-4.4.0-12.el9 |
CVE-2024-25260 | Anchore CVE | Low | elfutils-libs-0.190-2.el9 |
CVE-2020-12413 | Anchore CVE | Low | nss-softokn-freebl-3.90.0-7.el9_4 |
CVE-2020-18771 | Anchore CVE | Low | exiv2-0.27.5-2.el9 |
CVE-2022-27943 | Anchore CVE | Low | libgomp-11.4.1-3.el9 |
CVE-2017-7658 | Anchore CVE | Critical | servlet-api-4.0.6 |
CVE-2022-1056 | Anchore CVE | Low | libtiff-4.4.0-12.el9 |
CVE-2022-3555 | Anchore CVE | Low | libX11-common-1.7.0-9.el9 |
CVE-2022-3554 | Anchore CVE | Medium | libX11-common-1.7.0-9.el9 |
CVE-2023-25435 | Anchore CVE | Medium | libtiff-4.4.0-12.el9 |
CVE-2020-12413 | Anchore CVE | Low | nss-softokn-3.90.0-7.el9_4 |
CVE-2017-7657 | Anchore CVE | Critical | servlet-api-4.0.6 |
CVE-2023-2004 | Anchore CVE | Low | freetype-2.10.4-9.el9 |
CVE-2022-3857 | Anchore CVE | Low | java-17-openjdk-headless-1:17.0.11.0.9-2.el9 |
CVE-2021-3782 | Anchore CVE | Medium | libwayland-client-1.21.0-1.el9 |
CVE-2017-9735 | Anchore CVE | High | servlet-api-4.0.6 |
CVE-2020-12413 | Anchore CVE | Low | nss-util-3.90.0-7.el9_4 |
CVE-2020-12413 | Anchore CVE | Low | nss-3.90.0-7.el9_4 |
CVE-2021-25317 | Anchore CVE | Low | cups-libs-1:2.3.3op2-24.el9 |
CVE-2022-3555 | Anchore CVE | Low | libX11-xcb-1.7.0-9.el9 |
CVE-2020-12413 | Anchore CVE | Low | nspr-4.35.0-7.el9_4 |
CVE-2023-26048 | Anchore CVE | Medium | servlet-api-4.0.6 |
CVE-2023-4504 | Anchore CVE | Medium | cups-libs-1:2.3.3op2-24.el9 |
CVE-2021-31535 | Anchore CVE | High | libX11-xcb-1.7.0-9.el9 |
CVE-2022-3555 | Anchore CVE | Low | libX11-1.7.0-9.el9 |
CVE-2020-18771 | Anchore CVE | Low | exiv2-libs-0.27.5-2.el9 |
CVE-2021-3782 | Anchore CVE | Medium | libwayland-server-1.21.0-1.el9 |
CVE-2021-3782 | Anchore CVE | Medium | libwayland-cursor-1.21.0-1.el9 |
CVE-2022-3554 | Anchore CVE | Medium | libX11-1.7.0-9.el9 |
CVE-2024-23226 | Twistlock CVE | Critical | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2023-42950 | Twistlock CVE | Critical | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2024-23284 | Twistlock CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2024-23280 | Twistlock CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2024-23263 | Twistlock CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2024-23254 | Twistlock CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2023-42956 | Twistlock CVE | Medium | webkit2gtk3-jsc-2.42.5-1.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-udev-252-32.el9_4 |
CVE-2021-3997 | Twistlock CVE | Medium | systemd-252-32.el9_4 |
CVE-2023-42843 | Twistlock CVE | Medium | webkit2gtk3-jsc-2.42.5-1.el9 |
CVE-2024-2511 | Twistlock CVE | Low | openssl-3.0.7-27.el9 |
CVE-2024-29040 | Twistlock CVE | Medium | tpm2-tss-3.2.2-2.el9 |
CVE-2024-4603 | Twistlock CVE | Low | openssl-3.0.7-27.el9 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/apache/solr-9&tag=9.6.0&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/apache/solr-9&tag=9.6.0&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.