chore(findings): pingamster
Summary
pingamster has 16 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=pingamster&tag=v8.0.1&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-29156 | Anchore CVE | High | amster-8.0.1 | 0.92185 | false | ||
CVE-2025-48924 | Twistlock CVE | Medium | commons-lang_commons-lang-2.6 | 0.00258 | false | ||
CVE-2025-50106 | Anchore CVE | High | openjdk-17.0.15+6-LTS | 0.00174 | false | ||
CVE-2025-50106 | Twistlock CVE | High | java-17.0.15 | 0.00174 | false | ||
CVE-2025-30749 | Anchore CVE | High | openjdk-17.0.15+6-LTS | 0.00174 | false | ||
CVE-2025-30749 | Twistlock CVE | High | java-17.0.15 | 0.00174 | false | ||
CVE-2025-8916 | Twistlock CVE | Medium | org.bouncycastle_bcpkix-fips-2.0.7 | 0.00055 | false | ||
CVE-2025-8885 | Twistlock CVE | Medium | org.bouncycastle_bc-fips-2.0.0 | 0.00055 | false | ||
CVE-2025-50059 | Anchore CVE | High | openjdk-17.0.15+6-LTS | 0.00054 | false | ||
CVE-2025-50059 | Twistlock CVE | High | java-17.0.15 | 0.00054 | false | ||
CVE-2023-50572 | Anchore CVE | Medium | jline-2.14.6 | 0.00043 | false | ||
CVE-2025-30754 | Anchore CVE | Medium | openjdk-17.0.15+6-LTS | 0.00036 | false | ||
CVE-2025-30754 | Twistlock CVE | Medium | java-17.0.15 | 0.00036 | false | ||
GHSA-j288-q9x7-2f5v | Anchore CVE | Medium | commons-lang-2.6 | N/A | N/A | ||
GHSA-67mf-3cr5-8w23 | Anchore CVE | Medium | bc-fips-2.0.0 | N/A | N/A | ||
GHSA-4cx2-fc23-5wg6 | Anchore CVE | Medium | bcpkix-fips-2.0.7 | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=pingamster&tag=v8.0.1&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.