chore(findings): opensource/goharbor/notary-signer
Summary
opensource/goharbor/notary-signer has 114 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2021-38297 | Twistlock CVE | Critical | go-1.14.15 |
CVE-2021-38297 | Twistlock CVE | Critical | go-1.14.15 |
CVE-2022-23806 | Twistlock CVE | Critical | go-1.14.15 |
CVE-2022-23806 | Twistlock CVE | Critical | go-1.14.15 |
CVE-2022-30580 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30580 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-41715 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-41715 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-32189 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-32189 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30635 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30635 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30633 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30633 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30632 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30632 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30631 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30631 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30630 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-30630 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-2880 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-2880 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-2879 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-2879 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-28327 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-28327 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-28131 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-28131 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-27664 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-27664 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-24921 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-24921 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-24675 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-24675 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-23773 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-23773 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-23772 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-23772 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-44716 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-44716 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-41772 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-41772 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-41771 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-41771 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-39293 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-39293 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-33198 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-33198 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-33196 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-33196 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-33194 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-33194 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-29923 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-29923 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-27918 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-27918 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-33195 | Twistlock CVE | High | go-1.14.15 |
CVE-2021-33195 | Twistlock CVE | High | go-1.14.15 |
CVE-2022-32149 | Twistlock CVE | High | golang.org/x/text-v0.3.2 |
CVE-2022-27664 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20200202094626-16171245cfb2 |
CVE-2022-27191 | Twistlock CVE | High | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
CVE-2021-43565 | Twistlock CVE | High | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
CVE-2021-38561 | Twistlock CVE | High | golang.org/x/text-v0.3.2 |
CVE-2021-33194 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20200202094626-16171245cfb2 |
CVE-2020-29652 | Twistlock CVE | High | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
PRISMA-2022-0113 | Twistlock CVE | Medium | github.com/aws/aws-sdk-go-v1.17.7 |
CVE-2022-32148 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2022-32148 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2022-2582 | Twistlock CVE | Medium | github.com/aws/aws-sdk-go-v1.17.7 |
CVE-2022-1705 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2022-1705 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2021-34558 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2021-34558 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2021-36221 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2021-36221 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2021-31525 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2021-31525 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2020-29510 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2020-29510 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2022-1962 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2022-1962 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2022-41716 | Twistlock CVE | Medium | go-1.14.15 |
PRISMA-2022-0281 | Twistlock CVE | Medium | github.com/aws/aws-sdk-go-v1.17.7 |
PRISMA-2022-0164 | Twistlock CVE | Medium | github.com/aws/aws-sdk-go-v1.17.7 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2021-33197 | Twistlock CVE | Medium | go-1.14.15 |
CVE-2021-33197 | Twistlock CVE | Medium | go-1.14.15 |
GHSA-76wf-9vgp-pj7w | Twistlock CVE | Medium | github.com/aws/aws-sdk-go-v1.17.7 |
CVE-2022-29526 | Twistlock CVE | Medium | golang.org/x/sys-v0.0.0-20200212091648-12a6c2dcc1e4 |
CVE-2021-31525 | Twistlock CVE | Medium | golang.org/x/net-v0.0.0-20200202094626-16171245cfb2 |
CVE-2020-8911 | Twistlock CVE | Medium | github.com/aws/aws-sdk-go-v1.17.7 |
CVE-2022-30629 | Twistlock CVE | Low | go-1.14.15 |
CVE-2022-30629 | Twistlock CVE | Low | go-1.14.15 |
CVE-2022-41723 | Twistlock CVE | Low | golang.org/x/net-v0.0.0-20200202094626-16171245cfb2 |
CVE-2020-8912 | Twistlock CVE | Low | github.com/aws/aws-sdk-go-v1.17.7 |
GHSA-69cg-p879-7622 | Anchore CVE | High | golang.org/x/net-v0.0.0-20200202094626-16171245cfb2 |
GHSA-gwc9-m7rh-j2ww | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
GHSA-vvpx-j8f3-3w6h | Anchore CVE | Low | golang.org/x/net-v0.0.0-20200202094626-16171245cfb2 |
GHSA-h86h-8ppg-mxmh | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20200202094626-16171245cfb2 |
GHSA-69ch-w2m2-3vjp | Anchore CVE | High | golang.org/x/text-v0.3.2 |
GHSA-8c26-wmh5-6g9v | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
GHSA-83g2-8m93-v3w7 | Anchore CVE | High | golang.org/x/net-v0.0.0-20200202094626-16171245cfb2 |
GHSA-ppp9-7jff-5vj2 | Anchore CVE | High | golang.org/x/text-v0.3.2 |
GHSA-7f33-f4f5-xwgw | Anchore CVE | Low | github.com/aws/aws-sdk-go-v1.17.7 |
GHSA-76wf-9vgp-pj7w | Anchore CVE | Medium | github.com/aws/aws-sdk-go-v1.17.7 |
GHSA-3vm4-22fp-5rfm | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
GHSA-f5pg-7wfw-84q9 | Anchore CVE | Medium | github.com/aws/aws-sdk-go-v1.17.7 |
GHSA-p782-xgp4-8hr8 | Anchore CVE | Medium | golang.org/x/sys-v0.0.0-20200212091648-12a6c2dcc1e4 |
CCE-85987-6 | OSCAP Compliance | Medium | |
CVE-2023-25139 | Twistlock CVE | Medium | glibc-minimal-langpack-2.28-211.el8 |
CVE-2023-25139 | Twistlock CVE | Medium | glibc-2.28-211.el8 |
CVE-2023-25139 | Twistlock CVE | Medium | glibc-common-2.28-211.el8 |
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/opensource/goharbor/notary-signer/-/jobs/19301515
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Hardening::Approval" label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications -
Send approval request to Authorizing Official -
Close issue after approval from Authorizing Official
Note: If the above approval process is rejected for any reason, the
Approval
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 theApproval
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.