chore(findings): cloudbees/core/core-oc
Summary
cloudbees/core/core-oc has 23 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2018-1000021 | Anchore CVE | Medium | git-2.39.3-1.el8_8 |
CVE-2021-45941 | Anchore CVE | Medium | libbpf-0.5.0-1.el8 |
CVE-2023-50495 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 |
CVE-2023-51767 | Anchore CVE | Medium | openssh-clients-8.0p1-19.el8_9.2 |
CVE-2016-20012 | Anchore CVE | Low | openssh-clients-8.0p1-19.el8_9.2 |
CVE-2022-3606 | Anchore CVE | Low | libbpf-0.5.0-1.el8 |
CVE-2018-19217 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 |
CVE-2023-51767 | Anchore CVE | Medium | openssh-8.0p1-19.el8_9.2 |
CVE-2018-1000021 | Anchore CVE | Medium | git-core-2.39.3-1.el8_8 |
CVE-2018-15919 | Anchore CVE | Low | openssh-clients-8.0p1-19.el8_9.2 |
CVE-2018-15919 | Anchore CVE | Low | openssh-8.0p1-19.el8_9.2 |
CVE-2018-1000021 | Anchore CVE | Medium | git-core-doc-2.39.3-1.el8_8 |
CVE-2018-19211 | Anchore CVE | Low | ncurses-6.1-10.20180224.el8 |
GHSA-2wrp-6fg6-hmc5 | Anchore CVE | High | spring-web-5.3.33 |
CVE-2019-6110 | Anchore CVE | Low | openssh-clients-8.0p1-19.el8_9.2 |
CVE-2016-20012 | Anchore CVE | Low | openssh-8.0p1-19.el8_9.2 |
CVE-2018-1000021 | Anchore CVE | Medium | perl-Git-2.39.3-1.el8_8 |
CVE-2024-0727 | Anchore CVE | Low | openssl-1:1.1.1k-12.el8_9 |
CVE-2019-6110 | Anchore CVE | Low | openssh-8.0p1-19.el8_9.2 |
CVE-2021-45941 | Twistlock CVE | Medium | libbpf-0.5.0-1.el8 |
CVE-2021-45940 | Twistlock CVE | Medium | libbpf-0.5.0-1.el8 |
CVE-2024-22262 | Twistlock CVE | High | spring-web-5.3.33 |
CVE-2023-48795 | Twistlock CVE | Medium | jenkins-2.440.3-cb-3 |
VAT: https://vat.dso.mil/vat/image?imageName=cloudbees/core/core-oc&tag=2.440.3.7&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=cloudbees/core/core-oc&tag=2.440.3.7&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.