chore(findings): opensource/zalando/logical-backup
Summary
opensource/zalando/logical-backup has 23 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
addbb93c22e9b0988b8b40392a4538cb | Anchore Compliance | Low | |
CVE-2020-26159 | Anchore CVE | Medium | oniguruma-6.8.2-2.el8 |
CVE-2019-13224 | Anchore CVE | Medium | oniguruma-6.8.2-2.el8 |
CVE-2019-19012 | Anchore CVE | Medium | oniguruma-6.8.2-2.el8 |
GHSA-v8gr-m533-ghj9 | Anchore CVE | Low | cryptography-38.0.1 |
GHSA-v845-jxx5-vc9f | Anchore CVE | Medium | urllib3-1.26.12 |
CVE-2019-16163 | Anchore CVE | Medium | oniguruma-6.8.2-2.el8 |
CVE-2019-19203 | Anchore CVE | Medium | oniguruma-6.8.2-2.el8 |
CVE-2019-19204 | Anchore CVE | Medium | oniguruma-6.8.2-2.el8 |
GHSA-g4mx-q9vg-27p4 | Anchore CVE | Medium | urllib3-1.26.12 |
GHSA-mq26-g339-26xf | Anchore CVE | Medium | pip-22.3 |
CVE-2022-48560 | Anchore CVE | Medium | python3-libs-3.6.8-56.el8_9 |
CVE-2022-48560 | Anchore CVE | Medium | platform-python-3.6.8-56.el8_9 |
CVE-2022-48564 | Anchore CVE | Medium | python3-libs-3.6.8-56.el8_9 |
CVE-2022-48564 | Anchore CVE | Medium | platform-python-3.6.8-56.el8_9 |
CVE-2022-44840 | Anchore CVE | Low | gdb-gdbserver-8.2-20.el8 |
CVE-2023-45803 | Anchore CVE | Medium | python3-urllib3-1.24.2-5.el8 |
CVE-2018-25091 | Anchore CVE | Medium | python3-urllib3-1.24.2-5.el8 |
GHSA-v8gr-m533-ghj9 | Twistlock CVE | Low | cryptography-38.0.1 |
CVE-2020-26159 | Twistlock CVE | Medium | oniguruma-6.8.2-2.el8 |
CVE-2022-44840 | Twistlock CVE | Low | gdb-gdbserver-8.2-20.el8 |
CVE-2023-5981 | Twistlock CVE | Medium | gnutls-3.6.16-7.el8 |
CVE-2023-49083 | Twistlock CVE | Medium | cryptography-38.0.1 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/zalando/logical-backup&tag=v1.8.2&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/zalando/logical-backup&tag=v1.8.2&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.