chore(findings): big-bang/cypress
Summary
big-bang/cypress has 12 new findings discovered during continuous monitoring.
Layer: cypress/included:15.0.0 is EOL, please update if possible
Layer: opensource/nodejs/debian/nodejs:22.18.0 is EOL, please update if possible
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=big-bang/cypress&tag=15.0.0&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-0725 | Anchore CVE | Low | curl-7.88.1-10+deb12u12 | 0.01042 | false | ||
CVE-2025-0725 | Anchore CVE | Low | libcurl4-7.88.1-10+deb12u12 | 0.01042 | false | ||
CVE-2024-2379 | Anchore CVE | Low | curl-7.88.1-10+deb12u12 | 0.00247 | false | ||
CVE-2024-2379 | Anchore CVE | Low | libcurl4-7.88.1-10+deb12u12 | 0.00247 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.4 | 0.00054 | false | ||
CVE-2025-1767 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.33.3 | 0.00041 | false | ||
CVE-2025-5187 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.33.3 | 0.00020 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.4 | 0.00006 | false | ||
CVE-2024-7598 | Twistlock CVE | Low | k8s.io/kubernetes-v1.33.3 | 0.00006 | false | ||
CVE-2025-9714 | Twistlock CVE | Low | libxml2-2.9.14+dfsg-1.3~deb12u4 | N/A | false | ||
CVE-2025-57052 | Twistlock CVE | Low | cjson-1.7.15-1+deb12u2 | N/A | false | ||
GHSA-4x4m-3c2p-qppc | Anchore CVE | Medium | k8s.io/kubernetes-v1.33.3 | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=big-bang/cypress&tag=15.0.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.