chore(findings): jfrog/jfrog-xray/xray-persist
Summary
jfrog/jfrog-xray/xray-persist has 49 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-qppj-fm5r-hxr3 | Anchore CVE | Medium | golang.org/x/net-v0.13.0 |
GHSA-45x7-px36-x8w8 | Anchore CVE | Medium | golang.org/x/crypto-v0.11.0 |
GHSA-qppj-fm5r-hxr3 | Anchore CVE | Medium | golang.org/x/net-v0.12.0 |
GHSA-4374-p667-p6c8 | Anchore CVE | High | golang.org/x/net-v0.12.0 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.12.0 |
GHSA-45x7-px36-x8w8 | Anchore CVE | Medium | golang.org/x/crypto-v0.0.0-20220314234659-1baeb1ce4c0b |
GHSA-4374-p667-p6c8 | Anchore CVE | High | golang.org/x/net-v0.13.0 |
GHSA-mw99-9chc-xw7r | Anchore CVE | High | github.com/go-git/go-git/v5-v5.1.0 |
GHSA-jq35-85cj-fj4p | Anchore CVE | Medium | github.com/docker/docker-v20.10.24+incompatible |
GHSA-m425-mq94-257g | Anchore CVE | High | google.golang.org/grpc-v1.57.0 |
GHSA-qppj-fm5r-hxr3 | Anchore CVE | Medium | google.golang.org/grpc-v1.57.0 |
GHSA-449p-3h89-pw88 | Anchore CVE | Critical | github.com/go-git/go-git/v5-v5.1.0 |
GHSA-m7wr-2xf7-cm9p | Anchore CVE | Medium | github.com/jackc/pgx/v4-v4.17.0 |
GHSA-8r3f-844c-mc37 | Anchore CVE | Medium | google.golang.org/protobuf-v1.31.0 |
GHSA-7jwh-3vrq-q3m8 | Anchore CVE | Medium | github.com/jackc/pgproto3/v2-v2.3.1 |
GHSA-7jwh-3vrq-q3m8 | Anchore CVE | Medium | github.com/jackc/pgx/v4-v4.17.0 |
GHSA-mrww-27vc-gghv | Anchore CVE | Medium | github.com/jackc/pgx/v4-v4.17.0 |
GHSA-mrww-27vc-gghv | Anchore CVE | Medium | github.com/jackc/pgproto3/v2-v2.3.1 |
GHSA-xw73-rw38-6vjc | Anchore CVE | Medium | github.com/docker/docker-v20.10.24+incompatible |
GHSA-mq39-4gv4-mvpx | Anchore CVE | Medium | github.com/docker/docker-v20.10.24+incompatible |
GHSA-rhh4-rh7c-7r5v | Anchore CVE | Medium | github.com/mholt/archiver/v3-v3.5.1 |
GHSA-4v7x-pqxf-cx7m | Anchore CVE | Medium | golang.org/x/net-v0.13.0 |
GHSA-4v7x-pqxf-cx7m | Anchore CVE | Medium | golang.org/x/net-v0.12.0 |
CVE-2023-29409 | Anchore CVE | Medium | stdlib-go1.20.5 |
CVE-2023-29406 | Anchore CVE | Medium | stdlib-go1.20.5 |
CVE-2023-45285 | Anchore CVE | High | stdlib-go1.21.3 |
CVE-2023-39326 | Anchore CVE | Medium | stdlib-go1.21.3 |
CVE-2023-39326 | Anchore CVE | Medium | stdlib-go1.20.5 |
CVE-2023-39326 | Anchore CVE | Medium | stdlib-go1.21.3 |
CVE-2023-39323 | Anchore CVE | High | stdlib-go1.20.5 |
CVE-2023-39325 | Anchore CVE | High | stdlib-go1.20.5 |
CVE-2018-1121 | Anchore CVE | Low | procps-ng-3.3.15-14.el8 |
CVE-2023-39318 | Anchore CVE | Medium | stdlib-go1.20.5 |
CVE-2023-44487 | Anchore CVE | High | stdlib-go1.20.5 |
CVE-2023-45285 | Anchore CVE | High | stdlib-go1.20.5 |
CVE-2023-45285 | Anchore CVE | High | stdlib-go1.21.3 |
CVE-2023-39319 | Anchore CVE | Medium | stdlib-go1.20.5 |
CVE-2023-49569 | Twistlock CVE | Critical | github.com/go-git/go-git/v5-v5.1.0 |
CVE-2023-39325 | Twistlock CVE | High | golang.org/x/net/http2-v0.13.0 |
CVE-2023-44487 | Twistlock CVE | High | golang.org/x/net-v0.13.0 |
CVE-2023-44487 | Twistlock CVE | High | golang.org/x/net-v0.12.0 |
CVE-2023-44487 | Twistlock CVE | High | google.golang.org/grpc-v1.57.0 |
CVE-2023-49568 | Twistlock CVE | High | github.com/go-git/go-git/v5-v5.1.0 |
CVE-2023-3978 | Twistlock CVE | Medium | golang.org/x/net/html-v0.12.0 |
CVE-2023-48795 | Twistlock CVE | Medium | golang.org/x/crypto/ssh-v0.11.0 |
GHSA-jq35-85cj-fj4p | Twistlock CVE | Medium | github.com/docker/docker-v20.10.24 |
CVE-2024-27304 | Twistlock CVE | Medium | github.com/jackc/pgproto3/v2-v2.3.1 |
CVE-2024-24557 | Twistlock CVE | Medium | github.com/docker/docker-v20.10.24 |
CVE-2023-45288 | Twistlock CVE | Medium | golang.org/x/net/http2-v0.13.0 |
VAT: https://vat.dso.mil/vat/image?imageName=jfrog/jfrog-xray/xray-persist&tag=3.86.10&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=jfrog/jfrog-xray/xray-persist&tag=3.75.12&branch=master
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Hardening::Verification" 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.