chore(findings): spark-operator/spark-operator
Summary
spark-operator/spark-operator has 76 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-f9jg-8p32-2f55 | Anchore CVE | Low | k8s.io/kubernetes-v1.19.6 |
GHSA-qppj-fm5r-hxr3 | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
GHSA-8mjg-8c8g-6h85 | Anchore CVE | Medium | k8s.io/kubernetes-v1.19.6 |
GHSA-qh36-44jv-c8xj | Anchore CVE | Low | k8s.io/kubernetes-v1.19.6 |
GHSA-4374-p667-p6c8 | Anchore CVE | High | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
GHSA-vvpx-j8f3-3w6h | Anchore CVE | High | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
GHSA-cgcv-5272-97pr | Anchore CVE | Medium | k8s.io/kubernetes-v1.19.6 |
GHSA-35c7-w35f-xwgh | Anchore CVE | Medium | k8s.io/kubernetes-v1.19.6 |
GHSA-74j8-88mm-7496 | Anchore CVE | Medium | k8s.io/kubernetes-v1.19.6 |
GHSA-xc8m-28vv-4pjc | Anchore CVE | Medium | k8s.io/kubernetes-v1.19.6 |
GHSA-69ch-w2m2-3vjp | Anchore CVE | High | golang.org/x/text-v0.3.7 |
GHSA-fxg5-wq6x-vr4w | Anchore CVE | High | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
GHSA-j9wf-vvm6-4r9w | Anchore CVE | Medium | k8s.io/kubernetes-v1.19.6 |
GHSA-vw47-mr44-3jf9 | Anchore CVE | Low | k8s.io/kubernetes-v1.19.6 |
GHSA-69cg-p879-7622 | Anchore CVE | High | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
GHSA-mfv7-gq43-w965 | Anchore CVE | Medium | k8s.io/kubernetes-v1.19.6 |
GHSA-f5f7-6478-qm6p | Anchore CVE | High | k8s.io/kubernetes-v1.19.6 |
GHSA-qc2g-gmh6-95p4 | Anchore CVE | Medium | k8s.io/kubernetes-v1.19.6 |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
GHSA-g42g-737j-qx6j | Anchore CVE | Medium | k8s.io/kubernetes-v1.19.6 |
GHSA-q78c-gwqw-jcmc | Anchore CVE | High | k8s.io/kubernetes-v1.19.6 |
CVE-2023-2975 | Anchore CVE | Low | openssl-1:3.0.7-24.el9 |
CVE-2021-23840 | Anchore CVE | Medium | openssl-1:3.0.7-24.el9 |
CVE-2023-5678 | Anchore CVE | Low | openssl-1:3.0.7-24.el9 |
CVE-2023-3446 | Anchore CVE | Low | openssl-1:3.0.7-24.el9 |
CVE-2023-3817 | Anchore CVE | Low | openssl-1:3.0.7-24.el9 |
CVE-2023-5363 | Anchore CVE | Medium | openssl-1:3.0.7-24.el9 |
GHSA-7fxm-f474-hf8w | Anchore CVE | High | k8s.io/kubernetes-v1.19.6 |
GHSA-hq6q-c2x6-hmch | Anchore CVE | High | k8s.io/kubernetes-v1.19.6 |
CCE-88048-4 | OSCAP Compliance | Medium | |
CCE-83908-4 | OSCAP Compliance | Medium | |
CCE-83623-9 | OSCAP Compliance | Medium | |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.19.2 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.19.2 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.19.2 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.19.2 |
CVE-2023-24540 | Twistlock CVE | Critical | go-1.19.2 |
CVE-2023-24538 | Twistlock CVE | Critical | go-1.19.2 |
CVE-2021-25741 | Twistlock CVE | High | k8s.io/kubernetes-v1.19.6 |
CVE-2023-29403 | Twistlock CVE | High | go-1.19.2 |
PRISMA-2022-0227 | Twistlock CVE | High | github.com/emicklei/go-restful/v3-v3.8.0 |
CVE-2023-39325 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
CVE-2023-24537 | Twistlock CVE | High | go-1.19.2 |
CVE-2023-24536 | Twistlock CVE | High | go-1.19.2 |
CVE-2023-24534 | Twistlock CVE | High | go-1.19.2 |
CVE-2022-41725 | Twistlock CVE | High | go-1.19.2 |
CVE-2022-41724 | Twistlock CVE | High | go-1.19.2 |
CVE-2022-41723 | Twistlock CVE | High | go-1.19.2 |
CVE-2022-41723 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
CVE-2022-41721 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
CVE-2022-41716 | Twistlock CVE | High | go-1.19.2 |
CVE-2022-32149 | Twistlock CVE | High | golang.org/x/text-v0.3.7 |
CVE-2022-27664 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
CVE-2023-29400 | Twistlock CVE | High | go-1.19.2 |
CVE-2023-24539 | Twistlock CVE | High | go-1.19.2 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.19.2 |
CVE-2023-2728 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.19.6 |
CVE-2023-2727 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.19.6 |
CVE-2021-25735 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.19.6 |
CVE-2023-3978 | Twistlock CVE | Medium | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.19.2 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.19.2 |
CVE-2021-25736 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.19.6 |
CVE-2023-44487 | Twistlock CVE | Medium | golang.org/x/net-v0.0.0-20220722155237-a158d28d115b |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.19.2 |
CVE-2023-24532 | Twistlock CVE | Medium | go-1.19.2 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.19.2 |
CVE-2020-8554 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.19.6 |
CVE-2021-25737 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.19.6 |
CVE-2020-8564 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.19.6 |
CVE-2023-2431 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.19.6 |
CVE-2020-8561 | Twistlock CVE | Medium | k8s.io/kubernetes-v1.19.6 |
CVE-2021-25740 | Twistlock CVE | Low | k8s.io/kubernetes-v1.19.6 |
CVE-2020-8562 | Twistlock CVE | Low | k8s.io/kubernetes-v1.19.6 |
CVE-2021-25743 | Twistlock CVE | Low | k8s.io/kubernetes-v1.19.6 |
CVE-2023-5528 | Twistlock CVE | High | k8s.io/kubernetes-v1.19.6 |
VAT: https://vat.dso.mil/vat/image?imageName=spark-operator/spark-operator&tag=v1beta2-1.3.8-3.1.1&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=spark-operator/spark-operator&tag=v1beta2-1.3.8-3.1.1&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.