chore(findings): opensource/kubeflow/admission-webhook
Summary
opensource/kubeflow/admission-webhook has 44 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-vvpx-j8f3-3w6h | Anchore CVE | High | golang.org/x/net-v0.0.0-20211209124913-491a49abca63 |
GHSA-69cg-p879-7622 | Anchore CVE | High | golang.org/x/net-v0.0.0-20211209124913-491a49abca63 |
GHSA-69ch-w2m2-3vjp | Anchore CVE | High | golang.org/x/text-v0.3.7 |
GHSA-p782-xgp4-8hr8 | Anchore CVE | Medium | golang.org/x/sys-v0.0.0-20211029165221-6e7872819dc8 |
GHSA-hp87-p4gw-j4gq | Anchore CVE | High | gopkg.in/yaml.v3-v3.0.0-20210107192922-496545a6307b |
GHSA-4374-p667-p6c8 | Anchore CVE | High | golang.org/x/net-v0.0.0-20211209124913-491a49abca63 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20211209124913-491a49abca63 |
GHSA-qppj-fm5r-hxr3 | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20211209124913-491a49abca63 |
GHSA-8r3f-844c-mc37 | Anchore CVE | Medium | google.golang.org/protobuf-v1.27.1 |
GHSA-4v7x-pqxf-cx7m | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20211209124913-491a49abca63 |
CVE-2022-41724 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2022-41725 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-24539 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-24536 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-24540 | Anchore CVE | Critical | stdlib-go1.19.2 |
CVE-2023-45285 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-39319 | Anchore CVE | Medium | stdlib-go1.19.2 |
CVE-2023-29403 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-29404 | Anchore CVE | Critical | stdlib-go1.19.2 |
CVE-2023-39326 | Anchore CVE | Medium | stdlib-go1.19.2 |
CVE-2023-29409 | Anchore CVE | Medium | stdlib-go1.19.2 |
CVE-2023-24532 | Anchore CVE | Medium | stdlib-go1.19.2 |
CVE-2023-39318 | Anchore CVE | Medium | stdlib-go1.19.2 |
CVE-2023-29406 | Anchore CVE | Medium | stdlib-go1.19.2 |
CVE-2023-24537 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-29405 | Anchore CVE | Critical | stdlib-go1.19.2 |
CVE-2023-24538 | Anchore CVE | Critical | stdlib-go1.19.2 |
CVE-2022-41717 | Anchore CVE | Medium | stdlib-go1.19.2 |
CVE-2023-29402 | Anchore CVE | Critical | stdlib-go1.19.2 |
CVE-2023-24534 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-45287 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2022-41723 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-44487 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-39323 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2023-29400 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2022-41722 | Anchore CVE | High | stdlib-go1.19.2 |
CVE-2022-28948 | Twistlock CVE | High | gopkg.in/yaml.v3-v3.0.0-20210107192922-496545a6307b |
CVE-2023-39325 | Twistlock CVE | High | golang.org/x/net/http2-v0.0.0-20211209124913-491a49abca63 |
CVE-2022-41723 | Twistlock CVE | High | golang.org/x/net/http2-v0.0.0-20211209124913-491a49abca63 |
CVE-2022-27664 | Twistlock CVE | High | golang.org/x/net/http2-v0.0.0-20211209124913-491a49abca63 |
CVE-2023-44487 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20211209124913-491a49abca63 |
CVE-2022-41717 | Twistlock CVE | Medium | golang.org/x/net/http2-v0.0.0-20211209124913-491a49abca63 |
CVE-2022-29526 | Twistlock CVE | Medium | golang.org/x/sys/unix-v0.0.0-20211029165221-6e7872819dc8 |
CVE-2023-45288 | Twistlock CVE | Medium | golang.org/x/net/http2-v0.0.0-20211209124913-491a49abca63 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/kubeflow/admission-webhook&tag=1.6.1&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/kubeflow/admission-webhook&tag=1.6.1&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.