chore(findings): jfrog/jfrog-xray/xray-sbom
Summary
jfrog/jfrog-xray/xray-sbom has 34 new findings discovered during continuous monitoring.
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=jfrog/jfrog-xray/xray-sbom&tag=3.118.24&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-2024-0406 | Twistlock CVE | Medium | github.com/mholt/archiver-v2.1.0 | 0.13813 | false | ||
CVE-2025-3445 | Twistlock CVE | High | github.com/mholt/archiver-v2.1.0 | 0.00085 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.24.2 | 0.00053 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.9 | 0.00053 | false | ||
CVE-2025-47907 | Anchore CVE | High | stdlib-go1.23.9 | 0.00053 | false | ||
CVE-2025-58058 | Twistlock CVE | Medium | github.com/ulikunitz/xz-v0.5.12 | 0.00051 | false | ||
CVE-2025-47906 | Twistlock CVE | Low | os/exec-1.24.2 | 0.00017 | false | ||
CVE-2025-47906 | Twistlock CVE | Low | os/exec-1.23.9 | 0.00017 | false | ||
CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.24.2 | 0.00017 | false | ||
CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.9 | 0.00017 | false | ||
CVE-2025-47906 | Anchore CVE | Medium | stdlib-go1.23.9 | 0.00017 | false | ||
CVE-2025-22872 | Twistlock CVE | Medium | golang.org/x/net/html-v0.36.0 | 0.00017 | false | ||
CVE-2025-4673 | Twistlock CVE | Low | net/http-1.23.9 | 0.00014 | false | ||
CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.9 | 0.00014 | false | ||
CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.23.9 | 0.00014 | false | ||
CVE-2025-4673 | Anchore CVE | Medium | stdlib-go1.24.2 | 0.00014 | false | ||
CVE-2025-4673 | Twistlock CVE | Low | net/http-1.24.2 | 0.00014 | false | ||
CVE-2025-8556 | Twistlock CVE | Low | github.com/cloudflare/circl-v1.5.0 | 0.00012 | false | ||
CVE-2025-22874 | Twistlock CVE | Low | crypto/x509-1.24.2 | 0.00012 | false | ||
CVE-2025-22874 | Anchore CVE | High | stdlib-go1.24.2 | 0.00012 | false | ||
CVE-2025-54410 | Twistlock CVE | Low | github.com/docker/docker-v27.1.1 | 0.00006 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.9 | 0.00005 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.23.9 | 0.00005 | false | ||
CVE-2025-4674 | Anchore CVE | High | stdlib-go1.24.2 | 0.00005 | false | ||
PRISMA-2022-0394 | Twistlock CVE | Medium | github.com/gin-gonic/gin-v1.10.0 | N/A | N/A | ||
PRISMA-2022-0393 | Twistlock CVE | Medium | github.com/gin-gonic/gin-v1.10.0 | N/A | N/A | ||
PRISMA-2022-0164 | Twistlock CVE | Medium | github.com/aws/aws-sdk-go-v1.34.22 | N/A | N/A | ||
GHSA-vvgc-356p-c3xw | Anchore CVE | Medium | golang.org/x/net-v0.36.0 | N/A | N/A | ||
GHSA-jc7w-c686-c4v9 | Anchore CVE | Medium | github.com/ulikunitz/xz-v0.5.12 | N/A | N/A | ||
GHSA-7vpp-9cxj-q8gv | Anchore CVE | High | github.com/mholt/archiver-v2.1.0+incompatible | N/A | N/A | ||
GHSA-6v2p-p543-phr9 | Anchore CVE | High | golang.org/x/oauth2-v0.25.0 | N/A | N/A | ||
GHSA-6m8w-jc87-6cr7 | Anchore CVE | High | github.com/open-policy-agent/opa-v0.68.0 | N/A | N/A | ||
GHSA-4vq8-7jfc-9cvp | Anchore CVE | Low | github.com/docker/docker-v27.1.1+incompatible | N/A | N/A | ||
GHSA-2x5j-vhc8-9cwm | Anchore CVE | Low | github.com/cloudflare/circl-v1.5.0 | N/A | N/A |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=jfrog/jfrog-xray/xray-sbom&tag=3.118.24&branch=master
Tasks
Contributor:
-
Apply the StatusReview label to this issue for a merge request review
and wait for feedback
OR
-
Provide justifications for findings in the VAT (docs) -
Apply the StatusVerification label to this issue for a VAT justifications review
and wait for feedback
Iron Bank:
-
Review findings and justifications
Note: If the above process is rejected for any reason, the
Review
orVerification
label will be removed and the issue will be sent back toTo-Do
. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theReview
orVerification
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.