chore(findings): google/distroless11/base
Summary
google/distroless11/base has 25 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
cbff271f45d32e78dcc1979dbca9c14d | Anchore Compliance | Critical | |
4f9abc83a7a1c95e222b659e0fab27fa | Anchore Compliance | Low | |
CVE-2019-1010022 | Anchore CVE | Low | libc6-2.31-13+deb11u7 |
CVE-2010-0928 | Anchore CVE | Low | libssl1.1-1.1.1w-0+deb11u1 |
CVE-2007-6755 | Anchore CVE | Low | openssl-1.1.1w-0+deb11u1 |
CVE-2010-4756 | Anchore CVE | Low | libc6-2.31-13+deb11u7 |
CVE-2010-0928 | Anchore CVE | Low | openssl-1.1.1w-0+deb11u1 |
CVE-2019-1010025 | Anchore CVE | Low | libc6-2.31-13+deb11u7 |
CVE-2007-6755 | Anchore CVE | Low | libssl1.1-1.1.1w-0+deb11u1 |
CVE-2018-20796 | Anchore CVE | Low | libc6-2.31-13+deb11u7 |
CVE-2019-1010024 | Anchore CVE | Low | libc6-2.31-13+deb11u7 |
CVE-2019-9192 | Anchore CVE | Low | libc6-2.31-13+deb11u7 |
CVE-2019-1010023 | Anchore CVE | Low | libc6-2.31-13+deb11u7 |
CVE-2019-1010022 | Twistlock CVE | Low | glibc-2.31-13+deb11u7 |
CVE-2019-1010023 | Twistlock CVE | Low | glibc-2.31-13+deb11u7 |
CVE-2019-9192 | Twistlock CVE | Low | glibc-2.31-13+deb11u7 |
CVE-2018-20796 | Twistlock CVE | Low | glibc-2.31-13+deb11u7 |
CVE-2023-4813 | Twistlock CVE | Low | glibc-2.31-13+deb11u7 |
CVE-2023-4806 | Twistlock CVE | Low | glibc-2.31-13+deb11u7 |
CVE-2023-5678 | Twistlock CVE | Low | openssl-1.1.1w-0+deb11u1 |
CVE-2019-1010025 | Twistlock CVE | Low | glibc-2.31-13+deb11u7 |
CVE-2019-1010024 | Twistlock CVE | Low | glibc-2.31-13+deb11u7 |
CVE-2010-4756 | Twistlock CVE | Low | glibc-2.31-13+deb11u7 |
CVE-2010-0928 | Twistlock CVE | Low | openssl-1.1.1w-0+deb11u1 |
CVE-2007-6755 | Twistlock CVE | Low | openssl-1.1.1w-0+deb11u1 |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=google/distroless11/base&tag=nonroot&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.