chore(findings): big-bang/dind-alpine
Summary
big-bang/dind-alpine has 61 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=big-bang/dind-alpine&tag=28.3.1-dind-alpine3.22&branch=master
EPSS (Exploit Prediction Scoring System) provides an estimate of the likelihood that a vulnerability will be exploited in the wild.
KEV (Known Exploited Vulnerabilities) indicates whether a vulnerability is actively being exploited according to CISA.
id | source | severity | package | impact | workaround | epss_score | kev |
---|---|---|---|---|---|---|---|
CVE-2025-48384 | Twistlock CVE | Low | git-2.49.0-r0 | 0.04084 | true | ||
CVE-2025-48384 | Anchore CVE | High | git-2.49.0-r0 | 0.04084 | true | ||
CVE-2025-48384 | Anchore CVE | High | git-init-template-2.49.0-r0 | 0.04084 | true | ||
CVE-2025-48385 | Twistlock CVE | Low | git-2.49.0-r0 | 0.00112 | false | ||
CVE-2025-48385 | Anchore CVE | High | git-init-template-2.49.0-r0 | 0.00112 | false | ||
CVE-2025-48385 | Anchore CVE | High | git-2.49.0-r0 | 0.00112 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00054 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.10 | 0.00054 | false | ||
CVE-2024-10041 | Anchore CVE | Medium | linux-pam-1.7.0-r4 | 0.00032 | false | ||
CVE-2024-58251 | Anchore CVE | Low | ssl_client-1.37.0-r18 | 0.00031 | false | ||
CVE-2024-58251 | Anchore CVE | Low | busybox-1.37.0-r18 | 0.00031 | false | ||
CVE-2024-58251 | Anchore CVE | Low | busybox-binsh-1.37.0-r18 | 0.00031 | false | ||
CVE-2025-46835 | Twistlock CVE | Low | git-2.49.0-r0 | 0.00024 | false | ||
CVE-2025-46835 | Anchore CVE | High | git-init-template-2.49.0-r0 | 0.00024 | false | ||
CVE-2025-46835 | Anchore CVE | High | git-2.49.0-r0 | 0.00024 | false | ||
CVE-2025-27614 | Twistlock CVE | Low | git-2.49.0-r0 | 0.00024 | false | ||
CVE-2025-27614 | Anchore CVE | High | git-init-template-2.49.0-r0 | 0.00024 | false | ||
CVE-2025-27614 | Anchore CVE | High | git-2.49.0-r0 | 0.00024 | false | ||
CVE-2025-46334 | Twistlock CVE | Low | git-2.49.0-r0 | 0.00023 | false | ||
CVE-2025-46334 | Anchore CVE | High | git-init-template-2.49.0-r0 | 0.00023 | false | ||
CVE-2025-46334 | Anchore CVE | High | git-2.49.0-r0 | 0.00023 | false | ||
CVE-2025-46394 | Anchore CVE | Low | busybox-binsh-1.37.0-r18 | 0.00022 | false | ||
CVE-2025-46394 | Anchore CVE | Low | ssl_client-1.37.0-r18 | 0.00022 | false | ||
CVE-2025-46394 | Anchore CVE | Low | busybox-1.37.0-r18 | 0.00022 | false | ||
CVE-2025-27613 | Twistlock CVE | Low | git-2.49.0-r0 | 0.00020 | false | ||
CVE-2025-27613 | Anchore CVE | Low | git-init-template-2.49.0-r0 | 0.00020 | false | ||
CVE-2025-27613 | Anchore CVE | Low | git-2.49.0-r0 | 0.00020 | false | ||
CVE-2025-48386 | Twistlock CVE | Low | git-2.49.0-r0 | 0.00015 | false | ||
CVE-2025-48386 | Anchore CVE | Medium | git-2.49.0-r0 | 0.00015 | false | ||
CVE-2025-48386 | Anchore CVE | Medium | git-init-template-2.49.0-r0 | 0.00015 | false | ||
CVE-2025-54388 | Twistlock CVE | Medium | github.com/docker/docker-v28.2.2 | 0.00010 | false | ||
CVE-2025-54388 | Twistlock CVE | Medium | github.com/docker/docker-v28.3.1 | 0.00010 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.10 | 0.00006 | false | ||
cbff271f45d32e78dcc1979dbca9c14d | Anchore Compliance | Critical | N/A | N/A | |||
b499a7c53e6a0110b1f81fea37c2d0b5 | Anchore Compliance | Critical | N/A | N/A | |||
GO-2025-3900 | Twistlock CVE | Medium | github.com/go-viper/mapstructure/v2-v2.0.0 | N/A | N/A | ||
GO-2025-3900 | Twistlock CVE | Medium | github.com/go-viper/mapstructure/v2-v2.3.0 | N/A | N/A | ||
GO-2025-3787 | Twistlock CVE | Medium | github.com/go-viper/mapstructure/v2-v2.0.0 | N/A | N/A | ||
GHSA-x4rx-4gw3-53p4 | Anchore CVE | Medium | github.com/docker/docker-v28.3.1 | N/A | N/A | ||
GHSA-x4rx-4gw3-53p4 | Anchore CVE | Medium | github.com/docker/docker-v28.3.1 | N/A | N/A | ||
GHSA-x4rx-4gw3-53p4 | Anchore CVE | Medium | github.com/docker/docker-v28.3.1+incompatible | N/A | N/A | ||
GHSA-x4rx-4gw3-53p4 | Anchore CVE | Medium | github.com/docker/docker-v28.2.2+incompatible | N/A | N/A | ||
GHSA-fv92-fjc5-jj9h | Anchore CVE | Medium | github.com/go-viper/mapstructure/v2-v2.0.0 | N/A | N/A | ||
GHSA-2464-8j7c-4cjm | Anchore CVE | Medium | github.com/go-viper/mapstructure/v2-v2.3.0 | N/A | N/A | ||
GHSA-2464-8j7c-4cjm | Anchore CVE | Medium | github.com/go-viper/mapstructure/v2-v2.0.0 | N/A | N/A | ||
607066173c1603d068829adb64352176 | Anchore Compliance | Critical | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=big-bang/dind-alpine&tag=28.3.1-dind-alpine3.22&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.