chore(findings): valley-tech-systems/boringtun
Summary
valley-tech-systems/boringtun has 47 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2022-45061 | Twistlock CVE | Medium | platform-python-3.6.8-48.el8_7 |
CVE-2022-45061 | Twistlock CVE | Medium | python3-libs-3.6.8-48.el8_7 |
CVE-2022-36227 | Twistlock CVE | Low | libarchive-3.3.3-4.el8 |
CVE-2022-36227 | Anchore CVE | Low | libarchive-3.3.3-4.el8 |
CVE-2022-45061 | Anchore CVE | Medium | python3-libs-3.6.8-48.el8_7 |
CVE-2022-45061 | Anchore CVE | Medium | platform-python-3.6.8-48.el8_7 |
CVE-2007-4559 | Anchore CVE | Medium | python3-libs-3.6.8-48.el8_7 |
CVE-2007-4559 | Anchore CVE | Medium | platform-python-3.6.8-48.el8_7 |
CVE-2020-17049 | Twistlock CVE | Medium | krb5-libs-1.18.2-22.el8_7 |
CCE-86099-9 | OSCAP Compliance | Medium | |
CVE-2021-44568 | Twistlock CVE | Low | libsolv-0.7.20-4.el8_7 |
CVE-2021-44568 | Anchore CVE | Low | libsolv-0.7.20-4.el8_7 |
CVE-2022-3606 | Twistlock CVE | Medium | libbpf-0.5.0-1.el8 |
CVE-2022-40897 | Twistlock CVE | Medium | python3-setuptools-wheel-39.2.0-6.el8 |
CVE-2022-40897 | Twistlock CVE | Medium | platform-python-setuptools-39.2.0-6.el8 |
CVE-2022-40897 | Anchore CVE | Medium | python3-setuptools-wheel-39.2.0-6.el8 |
CVE-2022-40897 | Anchore CVE | Medium | platform-python-setuptools-39.2.0-6.el8 |
CVE-2022-46908 | Twistlock CVE | Medium | sqlite-libs-3.26.0-17.el8_7 |
CVE-2022-4415 | Twistlock CVE | Medium | systemd-libs-239-68.el8_7.2 |
CVE-2021-3826 | Twistlock CVE | Low | libstdc++-8.5.0-16.el8_7 |
CVE-2021-3826 | Twistlock CVE | Low | libgcc-8.5.0-16.el8_7 |
CVE-2019-19244 | Twistlock CVE | Low | sqlite-libs-3.26.0-17.el8_7 |
CVE-2022-43552 | Twistlock CVE | Low | libcurl-7.61.1-25.el8_7.1 |
CVE-2022-43552 | Twistlock CVE | Low | curl-7.61.1-25.el8_7.1 |
CVE-2022-27943 | Twistlock CVE | Low | libgcc-8.5.0-16.el8_7 |
CVE-2022-27943 | Twistlock CVE | Low | libstdc++-8.5.0-16.el8_7 |
CVE-2021-3997 | Twistlock CVE | Low | systemd-libs-239-68.el8_7.2 |
CVE-2018-1000654 | Twistlock CVE | Low | libtasn1-4.13-4.el8_7 |
CVE-2021-46195 | Twistlock CVE | Low | libgcc-8.5.0-16.el8_7 |
CVE-2021-46195 | Twistlock CVE | Low | libstdc++-8.5.0-16.el8_7 |
CVE-2019-9937 | Twistlock CVE | Low | sqlite-libs-3.26.0-17.el8_7 |
CVE-2019-9936 | Twistlock CVE | Low | sqlite-libs-3.26.0-17.el8_7 |
CVE-2019-14250 | Twistlock CVE | Low | libgcc-8.5.0-16.el8_7 |
CVE-2019-14250 | Twistlock CVE | Low | libstdc++-8.5.0-16.el8_7 |
CVE-2018-20657 | Twistlock CVE | Low | libstdc++-8.5.0-16.el8_7 |
CVE-2018-20657 | Twistlock CVE | Low | libgcc-8.5.0-16.el8_7 |
CVE-2022-35252 | Twistlock CVE | Low | libcurl-7.61.1-25.el8_7.1 |
CVE-2022-35252 | Twistlock CVE | Low | curl-7.61.1-25.el8_7.1 |
CVE-2022-4415 | Anchore CVE | Medium | systemd-libs-239-68.el8_7.2 |
CVE-2022-43552 | Anchore CVE | Low | curl-7.61.1-25.el8_7.1 |
CVE-2022-35252 | Anchore CVE | Low | curl-7.61.1-25.el8_7.1 |
CVE-2022-43552 | Anchore CVE | Low | libcurl-7.61.1-25.el8_7.1 |
CVE-2022-35252 | Anchore CVE | Low | libcurl-7.61.1-25.el8_7.1 |
CVE-2022-47629 | Twistlock CVE | Critical | libksba-1.3.5-8.el8_6 |
CVE-2022-45873 | Twistlock CVE | Medium | systemd-libs-239-68.el8_7.2 |
CVE-2022-47629 | Anchore CVE | High | libksba-1.3.5-8.el8_6 |
CVE-2022-23990 | Twistlock CVE | Medium | expat-2.2.5-10.el8_7.1 |
VAT: https://vat.dso.mil/vat/image?imageName=valley-tech-systems/boringtun&tag=0.4.0&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/valley-tech-systems/boringtun/-/jobs/16330898
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.