chore(findings): opensource/kubeflow/access-management
Summary
opensource/kubeflow/access-management has 65 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-8cfg-vx93-jvxw | Anchore CVE | Medium | k8s.io/client-go-v0.0.0-20190528110200-4f3abb12cae2 |
GHSA-cg3q-j54f-5p7p | Anchore CVE | High | github.com/prometheus/client_golang-v0.9.2 |
GHSA-vvpx-j8f3-3w6h | Anchore CVE | High | golang.org/x/net-v0.0.0-20200602114024-627f9648deb9 |
GHSA-8c26-wmh5-6g9v | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
GHSA-gwc9-m7rh-j2ww | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
GHSA-69cg-p879-7622 | Anchore CVE | High | golang.org/x/net-v0.0.0-20200602114024-627f9648deb9 |
GHSA-69ch-w2m2-3vjp | Anchore CVE | High | golang.org/x/text-v0.3.5 |
GHSA-jmrx-5g74-6v2f | Anchore CVE | Medium | k8s.io/client-go-v0.0.0-20190528110200-4f3abb12cae2 |
GHSA-83g2-8m93-v3w7 | Anchore CVE | High | golang.org/x/net-v0.0.0-20200602114024-627f9648deb9 |
GHSA-3vm4-22fp-5rfm | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
GHSA-h86h-8ppg-mxmh | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20200602114024-627f9648deb9 |
GHSA-ppp9-7jff-5vj2 | Anchore CVE | High | golang.org/x/text-v0.3.5 |
GHSA-p782-xgp4-8hr8 | Anchore CVE | Medium | golang.org/x/sys-v0.0.0-20200323222414-85ca7c5b95cd |
GHSA-74fp-r6jw-h4mp | Anchore CVE | High | k8s.io/apimachinery-v0.0.0-20190221084156-01f179d85dbc |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20200602114024-627f9648deb9 |
GHSA-4374-p667-p6c8 | Anchore CVE | High | golang.org/x/net-v0.0.0-20200602114024-627f9648deb9 |
GHSA-qppj-fm5r-hxr3 | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20200602114024-627f9648deb9 |
GHSA-45x7-px36-x8w8 | Anchore CVE | Medium | golang.org/x/crypto-v0.0.0-20200302210943-78000ba7a073 |
GHSA-4v7x-pqxf-cx7m | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20200602114024-627f9648deb9 |
CVE-2023-29402 | Anchore CVE | Critical | stdlib-go1.17.13 |
CVE-2022-41715 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-29405 | Anchore CVE | Critical | stdlib-go1.17.13 |
CVE-2023-39323 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2022-2879 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-39319 | Anchore CVE | Medium | stdlib-go1.17.13 |
CVE-2023-45285 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-24536 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-29406 | Anchore CVE | Medium | stdlib-go1.17.13 |
CVE-2022-41723 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2022-27664 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2022-41725 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2022-41717 | Anchore CVE | Medium | stdlib-go1.17.13 |
CVE-2023-24532 | Anchore CVE | Medium | stdlib-go1.17.13 |
CVE-2023-29403 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-24538 | Anchore CVE | Critical | stdlib-go1.17.13 |
CVE-2023-44487 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-24539 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2022-41724 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-39326 | Anchore CVE | Medium | stdlib-go1.17.13 |
CVE-2023-29409 | Anchore CVE | Medium | stdlib-go1.17.13 |
CVE-2023-29400 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-29404 | Anchore CVE | Critical | stdlib-go1.17.13 |
CVE-2023-24540 | Anchore CVE | Critical | stdlib-go1.17.13 |
CVE-2022-2880 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-24534 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-39318 | Anchore CVE | Medium | stdlib-go1.17.13 |
CVE-2023-24537 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2023-45287 | Anchore CVE | High | stdlib-go1.17.13 |
CVE-2022-41722 | Anchore CVE | High | stdlib-go1.17.13 |
GHSA-33c5-9fx5-fvjm | Anchore CVE | Medium | k8s.io/apimachinery-v0.0.0-20190221084156-01f179d85dbc |
CVE-2022-21698 | Twistlock CVE | High | github.com/prometheus/client_golang/prometheus/promhttp-v0.9.2 |
CVE-2023-39325 | Twistlock CVE | High | golang.org/x/net/http2-v0.0.0-20200602114024-627f9648deb9 |
CVE-2022-41723 | Twistlock CVE | High | golang.org/x/net/http2-v0.0.0-20200602114024-627f9648deb9 |
CVE-2022-27664 | Twistlock CVE | High | golang.org/x/net/http2-v0.0.0-20200602114024-627f9648deb9 |
CVE-2021-44716 | Twistlock CVE | High | golang.org/x/net/http2-v0.0.0-20200602114024-627f9648deb9 |
CVE-2023-44487 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20200602114024-627f9648deb9 |
GO-2022-0965 | Twistlock CVE | High | k8s.io/apimachinery/pkg/runtime/serializer/json-v0.0.0-20190221084156-01f179d85dbc |
GO-2022-0965 | Twistlock CVE | High | k8s.io/apimachinery/pkg/util/json-v0.0.0-20190221084156-01f179d85dbc |
CVE-2019-11250 | Twistlock CVE | Medium | k8s.io/client-go/transport-v0.0.0-20190528110200-4f3abb12cae2 |
CVE-2021-31525 | Twistlock CVE | Medium | golang.org/x/net/http/httpguts-v0.0.0-20200602114024-627f9648deb9 |
CVE-2020-8565 | Twistlock CVE | Medium | k8s.io/client-go/transport-v0.0.0-20190528110200-4f3abb12cae2 |
CVE-2022-41717 | Twistlock CVE | Medium | golang.org/x/net/http2-v0.0.0-20200602114024-627f9648deb9 |
CVE-2022-29526 | Twistlock CVE | Medium | golang.org/x/sys/unix-v0.0.0-20200323222414-85ca7c5b95cd |
CVE-2023-45288 | Twistlock CVE | Medium | golang.org/x/net/http2-v0.0.0-20200602114024-627f9648deb9 |
CVE-2020-8559 | Twistlock CVE | Medium | k8s.io/apimachinery-v0.0.0-20190221084156-01f179d85dbc |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/kubeflow/access-management&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/access-management&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.