chore(findings): jfrog/jfrog-xray/xray-rabbitmq
Summary
jfrog/jfrog-xray/xray-rabbitmq has 69 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-f3fp-gc8g-vw66 | Anchore CVE | Medium | github.com/opencontainers/runc-v1.1.0 |
GHSA-g2j6-57v7-gm8c | Anchore CVE | Medium | github.com/opencontainers/runc-v1.1.0 |
GHSA-m8cg-xc2p-r3fc | Anchore CVE | Low | github.com/opencontainers/runc-v1.1.0 |
GHSA-vpvm-3wq2-2wvm | Anchore CVE | High | github.com/opencontainers/runc-v1.1.0 |
GHSA-xr7r-f8xq-vfvv | Anchore CVE | High | github.com/opencontainers/runc-v1.1.0 |
CVE-2024-2511 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2022-27664 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-0464 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2022-30580 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-29405 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2022-30635 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-45287 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-24534 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-41715 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2018-1121 | Anchore CVE | Low | procps-ng-3.3.15-14.el8 |
CVE-2023-24532 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2023-29406 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2022-30630 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-41725 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-2004 | Anchore CVE | Low | freetype-2.9.1-9.el8 |
CVE-2022-30632 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-39326 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2023-29404 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2023-0466 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2022-30629 | Anchore CVE | Low | stdlib-go1.18.2 |
CVE-2023-29409 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2023-2650 | Anchore CVE | Medium | openssl-1:1.1.1k-12.el8_9 |
CVE-2023-24539 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-39318 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2023-24538 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2022-28131 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-29402 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2022-41723 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-41724 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2024-0727 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2023-0465 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2022-32148 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2022-1962 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2022-30633 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-41717 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2022-1705 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2022-32189 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-3857 | Anchore CVE | Low | libpng-2:1.6.34-5.el8 |
CVE-2019-7317 | Anchore CVE | Low | libpng-2:1.6.34-5.el8 |
CVE-2023-45285 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-24540 | Anchore CVE | Critical | stdlib-go1.18.2 |
CVE-2023-39323 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-2880 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-2879 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-24537 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-24536 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-44487 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2022-30631 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-29400 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-29403 | Anchore CVE | High | stdlib-go1.18.2 |
CVE-2023-39319 | Anchore CVE | Medium | stdlib-go1.18.2 |
CVE-2024-21626 | Twistlock CVE | High | github.com/opencontainers/runc-v1.1.0 |
CVE-2023-27561 | Twistlock CVE | High | github.com/opencontainers/runc-v1.1.0 |
CVE-2023-28642 | Twistlock CVE | Medium | github.com/opencontainers/runc-v1.1.0 |
CVE-2022-29162 | Twistlock CVE | Medium | github.com/opencontainers/runc-v1.1.0 |
CVE-2023-0464 | Twistlock CVE | Low | openssl-1.1.1k-12.el8_9 |
CVE-2024-0727 | Twistlock CVE | Low | openssl-1.1.1k-12.el8_9 |
CVE-2022-3857 | Twistlock CVE | Low | libpng-1.6.34-5.el8 |
CVE-2023-0466 | Twistlock CVE | Low | openssl-1.1.1k-12.el8_9 |
CVE-2023-0465 | Twistlock CVE | Low | openssl-1.1.1k-12.el8_9 |
CVE-2019-7317 | Twistlock CVE | Low | libpng-1.6.34-5.el8 |
CVE-2023-25809 | Twistlock CVE | Low | github.com/opencontainers/runc-v1.1.0 |
CVE-2024-2511 | Twistlock CVE | Low | openssl-1.1.1k-12.el8_9 |
GHSA-c5pj-mqfh-rvc3 | Twistlock CVE | High | github.com/opencontainers/runc-v1.1.0 |
VAT: https://vat.dso.mil/vat/image?imageName=jfrog/jfrog-xray/xray-rabbitmq&tag=3.11.10-debian-11-r5&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/jfrog/jfrog-xray/xray-rabbitmq/-/jobs/23421736
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.