chore(findings): opensource/canastawiki/canasta
Summary
opensource/canastawiki/canasta has 10 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/canastawiki/canasta&tag=1.39.8&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-2021-4156 | Anchore CVE | High | libsndfile1-1.0.31-2+deb11u1 | 0.00112 | false | ||
CVE-2021-4156 | Twistlock CVE | Low | libsndfile-1.0.31-2+deb11u1 | 0.00112 | false | ||
CVE-2025-52194 | Anchore CVE | High | libsndfile1-1.0.31-2+deb11u1 | 0.00083 | false | ||
CVE-2025-52194 | Twistlock CVE | Low | libsndfile-1.0.31-2+deb11u1 | 0.00083 | false | ||
CVE-2024-50613 | Anchore CVE | Medium | libsndfile1-1.0.31-2+deb11u1 | 0.00067 | false | ||
CVE-2024-50613 | Twistlock CVE | Medium | libsndfile-1.0.31-2+deb11u1 | 0.00067 | false | ||
CVE-2024-50612 | Anchore CVE | Medium | libsndfile1-1.0.31-2+deb11u1 | 0.00043 | false | ||
CVE-2022-33065 | Anchore CVE | High | libsndfile1-1.0.31-2+deb11u1 | 0.00024 | false | ||
CVE-2022-33064 | Anchore CVE | High | libsndfile1-1.0.31-2+deb11u1 | 0.00023 | false | ||
CVE-2022-33064 | Twistlock CVE | Low | libsndfile-1.0.31-2+deb11u1 | 0.00023 | false |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/canastawiki/canasta&tag=1.39.8&branch=master
Novel Tidelift Findings (Experimental)
opensource/canastawiki/canasta has 23 novel Tidelift findings discovered during continuous monitoring.
NOTE: This table is for Iron Bank evaluation and testing purposes. No action required by vendors.
id | cvss score | package | impact | workaround | epss_score | kev |
---|---|---|---|---|---|---|
CVE-2024-45293 | 7.5 | phpoffice/phpspreadsheet-1.19.0 | 0.21472 | false | ||
CVE-2021-27291 | 7.5 | Pygments-2.7.1 | Most users of Pygments are highlighting code in arbitrary programming languages and from userattackersupplied code. | Could limit or check the size of usersupplied code to be highlighted before calling Pygments to highlight it, although may not be appropriate given code can legitimately be of significant sizelength. | 0.02326 | false |
CVE-2023-28447 | 7.1 | smarty/smarty-v3.1.46 | 0.00375 | false | ||
CVE-2018-25047 | 5.4 | smarty/smarty-v3.1.46 | 0.00290 | false | ||
CVE-2024-45060 | 6.1 | phpoffice/phpspreadsheet-1.19.0 | 0.00227 | false | ||
CVE-2024-45292 | 5.4 | phpoffice/phpspreadsheet-1.19.0 | 0.00215 | false | ||
CVE-2025-23210 | 4.8 | phpoffice/phpspreadsheet-1.19.0 | 0.00151 | false | ||
CVE-2024-56408 | 8.3 | phpoffice/phpspreadsheet-1.19.0 | 0.00121 | false | ||
CVE-2021-20270 | 7.5 | Pygments-2.7.1 | 0.00119 | false | ||
CVE-2024-45046 | 5.4 | phpoffice/phpspreadsheet-1.19.0 | 0.00112 | false | ||
CVE-2024-35226 | 7.3 | smarty/smarty-v3.1.46 | 0.00103 | false | ||
CVE-2024-56412 | 5.4 | phpoffice/phpspreadsheet-1.19.0 | 0.00090 | false | ||
CVE-2024-56411 | 5.4 | phpoffice/phpspreadsheet-1.19.0 | 0.00090 | false | ||
CVE-2024-56410 | 5.4 | phpoffice/phpspreadsheet-1.19.0 | 0.00090 | false | ||
CVE-2024-56409 | 8.3 | phpoffice/phpspreadsheet-1.19.0 | 0.00090 | false | ||
CVE-2024-56366 | 8.3 | phpoffice/phpspreadsheet-1.19.0 | 0.00090 | false | ||
CVE-2024-56365 | 8.3 | phpoffice/phpspreadsheet-1.19.0 | 0.00090 | false | ||
CVE-2025-22131 | 6.1 | phpoffice/phpspreadsheet-1.19.0 | 0.00089 | false | ||
CVE-2025-54370 | 8.7 | phpoffice/phpspreadsheet-1.19.0 | 0.00064 | false | ||
CVE-2024-45048 | 8.7 | phpoffice/phpspreadsheet-1.19.0 | 0.00051 | false | ||
CVE-2024-47873 | 7.5 | phpoffice/phpspreadsheet-1.19.0 | 0.00046 | false | ||
CVE-2024-48917 | 7.5 | phpoffice/phpspreadsheet-1.19.0 | 0.00045 | false | ||
CVE-2025-45769 | firebase/php-jwt-v6.10.1 | 0.00008 | false |
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.