chore(findings): hashicorp/vault
Summary
hashicorp/vault has 75 new findings discovered during continuous monitoring.
Information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=hashicorp/vault&tag=1.13.13&branch=master
id | source | severity | package |
---|---|---|---|
GHSA-9763-4f94-gfch | Anchore CVE | High | github.com/cloudflare/circl-v1.3.3 |
GHSA-5x4g-q5rc-36jp | Anchore CVE | Low | go.etcd.io/etcd/client/pkg/v3-v3.0.0-20210928084031-3df272774672 |
GHSA-mrww-27vc-gghv | Anchore CVE | Medium | github.com/jackc/pgx-v3.3.0+incompatible |
GHSA-m7wr-2xf7-cm9p | Anchore CVE | Medium | github.com/jackc/pgx-v3.3.0+incompatible |
GHSA-c5q2-7r4c-mv6g | Anchore CVE | Medium | github.com/go-jose/go-jose/v3-v3.0.1 |
GHSA-8r3f-844c-mc37 | Anchore CVE | Medium | google.golang.org/protobuf-v1.31.0 |
GHSA-m7wr-2xf7-cm9p | Anchore CVE | Medium | github.com/jackc/pgx/v4-v4.18.1 |
GHSA-mrww-27vc-gghv | Anchore CVE | Medium | github.com/jackc/pgx/v4-v4.18.1 |
GHSA-mrww-27vc-gghv | Anchore CVE | Medium | github.com/jackc/pgproto3/v2-v2.3.2 |
GHSA-7jwh-3vrq-q3m8 | Anchore CVE | Medium | github.com/jackc/pgx/v4-v4.18.1 |
GHSA-7jwh-3vrq-q3m8 | Anchore CVE | Medium | github.com/jackc/pgproto3/v2-v2.3.2 |
GHSA-rhh4-rh7c-7r5v | Anchore CVE | Medium | github.com/mholt/archiver/v3-v3.5.1 |
GHSA-4v7x-pqxf-cx7m | Anchore CVE | Medium | golang.org/x/net-v0.18.0 |
CVE-2022-0530 | Anchore CVE | Low | unzip-6.0-46.el8 |
CVE-2022-0529 | Anchore CVE | Low | unzip-6.0-46.el8 |
CVE-2021-4217 | Anchore CVE | Low | unzip-6.0-46.el8 |
CVE-2023-6597 | OSCAP Compliance | Medium | |
CVE-2024-0450 | OSCAP Compliance | Medium | |
CVE-2024-33599 | OSCAP Compliance | Medium | |
CVE-2024-33600 | OSCAP Compliance | Medium | |
CVE-2024-33601 | OSCAP Compliance | Medium | |
CVE-2024-33602 | OSCAP Compliance | Medium | |
CVE-2024-25062 | OSCAP Compliance | Medium | |
CVE-2024-28180 | Twistlock CVE | Medium | github.com/go-jose/go-jose/v3-v3.0.1 |
CVE-2024-27304 | Twistlock CVE | Medium | github.com/jackc/pgproto3/v2-v2.3.2 |
CVE-2024-28180 | Twistlock CVE | Medium | gopkg.in/square/go-jose.v2-v2.6.0 |
CVE-2023-45288 | Twistlock CVE | Medium | golang.org/x/net/http2-v0.18.0 |
PRISMA-2022-0168 | Twistlock CVE | High | pip-9.0.3 |
PRISMA-2022-0227 | Twistlock CVE | High | github.com/emicklei/go-restful/v3-v3.8.0 |
PRISMA-2023-0056 | Twistlock CVE | Medium | github.com/sirupsen/logrus-v1.9.0 |
CVE-2024-0406 | Twistlock CVE | Medium | github.com/mholt/archiver/v3-v3.5.1 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-minimal-langpack-2.28-251.el8_10.1 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-common-2.28-251.el8_10.1 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-2.28-251.el8_10.1 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-gconv-extra-2.28-251.el8_10.1 |
CVE-2024-33599 | Twistlock CVE | Critical | glibc-langpack-en-2.28-251.el8_10.1 |
CVE-2024-35195 | Twistlock CVE | Medium | platform-python-pip-9.0.3-24.el8 |
CVE-2024-35195 | Twistlock CVE | Medium | python3-pip-wheel-9.0.3-24.el8 |
CVE-2024-35195 | Twistlock CVE | Medium | python3-requests-2.20.0-3.el8_8 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-2.28-251.el8_10.1 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-langpack-en-2.28-251.el8_10.1 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-minimal-langpack-2.28-251.el8_10.1 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-gconv-extra-2.28-251.el8_10.1 |
CVE-2024-33600 | Twistlock CVE | Medium | glibc-common-2.28-251.el8_10.1 |
CVE-2023-2953 | OSCAP Compliance | Medium | |
CVE-2024-3651 | OSCAP Compliance | Medium | |
CVE-2024-28182 | OSCAP Compliance | Medium | |
CVE-2024-4741 | Twistlock CVE | Low | openssl-libs-1.1.1k-12.el8_9 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-langpack-en-2.28-251.el8_10.1 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-minimal-langpack-2.28-251.el8_10.1 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-2.28-251.el8_10.1 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-common-2.28-251.el8_10.1 |
CVE-2024-33602 | Twistlock CVE | Low | glibc-gconv-extra-2.28-251.el8_10.1 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-langpack-en-2.28-251.el8_10.1 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-gconv-extra-2.28-251.el8_10.1 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-2.28-251.el8_10.1 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-common-2.28-251.el8_10.1 |
CVE-2024-33601 | Twistlock CVE | Low | glibc-minimal-langpack-2.28-251.el8_10.1 |
GHSA-m5vv-6r4h-3vj9 | Twistlock CVE | Medium | github.com/Azure/azure-sdk-for-go/sdk/azidentity-v1.2.1 |
CVE-2024-35328 | Twistlock CVE | Medium | libyaml-0.1.7-5.el8 |
CVE-2024-4032 | Twistlock CVE | Low | platform-python-3.6.8-59.el8 |
CVE-2024-4032 | Twistlock CVE | Low | python3-libs-3.6.8-59.el8 |
CVE-2024-35326 | Twistlock CVE | Medium | libyaml-0.1.7-5.el8 |
CVE-2024-35325 | Twistlock CVE | Medium | libyaml-0.1.7-5.el8 |
GHSA-v6v8-xj6m-xwqh | Twistlock CVE | Medium | github.com/hashicorp/go-retryablehttp-v0.7.2 |
GO-2024-2947 | Twistlock CVE | Low | github.com/hashicorp/go-retryablehttp-v0.7.2 |
CVE-2024-37891 | Twistlock CVE | Medium | python3-urllib3-1.24.2-7.el8 |
CVE-2024-37371 | Twistlock CVE | Medium | krb5-libs-1.18.2-27.el8_10 |
CVE-2024-37370 | Twistlock CVE | Medium | krb5-libs-1.18.2-27.el8_10 |
CVE-2024-5535 | Twistlock CVE | Low | openssl-libs-1.1.1k-12.el8_9 |
CVE-2024-5642 | Twistlock CVE | Low | python3-libs-3.6.8-59.el8 |
CVE-2024-5642 | Twistlock CVE | Low | platform-python-3.6.8-59.el8 |
GO-2024-2918 | Twistlock CVE | Low | github.com/Azure/azure-sdk-for-go/sdk/azidentity-v1.2.1 |
CVE-2023-24531 | Twistlock CVE | Low | go-1.20.12 |
CVE-2024-3651 | Twistlock CVE | Medium | python3-idna-2.5-5.el8 |
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=hashicorp/vault&tag=1.13.13&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.