chore(findings): hashicorp/secure-secrets-management/vault-enterprise
Summary
hashicorp/secure-secrets-management/vault-enterprise has 79 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-3839-6r69-m497 | Anchore CVE | Critical | github.com/Masterminds/goutils-v1.1.0 |
GHSA-vvpx-j8f3-3w6h | Anchore CVE | High | golang.org/x/net-v0.0.0-20220127200216-cd36cc0744dd |
GHSA-8c26-wmh5-6g9v | Anchore CVE | High | golang.org/x/crypto-v0.0.0-20220208050332-20e1d8d225ab |
GHSA-69cg-p879-7622 | Anchore CVE | High | golang.org/x/net-v0.0.0-20220127200216-cd36cc0744dd |
GHSA-69ch-w2m2-3vjp | Anchore CVE | High | golang.org/x/text-v0.3.7 |
GHSA-8449-7gc2-pwrp | Anchore CVE | High | github.com/hashicorp/consul-template-v0.28.1-0.20220415203157-ebf2f3dfe745 |
GHSA-p782-xgp4-8hr8 | Anchore CVE | Medium | golang.org/x/sys-v0.0.0-20220207234003-57398862261d |
GHSA-6wrf-mxfj-pf5p | Anchore CVE | Medium | github.com/docker/docker-v20.10.10+incompatible |
GHSA-232p-vwff-86mp | Anchore CVE | High | github.com/docker/docker-v20.10.10+incompatible |
GHSA-33pg-m6jh-5237 | Anchore CVE | Medium | github.com/docker/docker-v20.10.10+incompatible |
GHSA-fwv2-65wh-2w8c | Anchore CVE | High | github.com/snowflakedb/gosnowflake-v1.6.3 |
GHSA-hp87-p4gw-j4gq | Anchore CVE | High | gopkg.in/yaml.v3-v3.0.0-20210107192922-496545a6307b |
GHSA-4374-p667-p6c8 | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20220127200216-cd36cc0744dd |
GHSA-2wrh-6pvc-2jm9 | Anchore CVE | Medium | golang.org/x/net-v0.0.0-20220127200216-cd36cc0744dd |
CVE-2022-0530 | Twistlock CVE | Low | unzip-6.0-46.el8 |
CVE-2022-0529 | Twistlock CVE | Low | unzip-6.0-46.el8 |
CVE-2021-4217 | Twistlock CVE | Low | unzip-6.0-46.el8 |
CVE-2022-40186 | Twistlock CVE | Critical | vault-1.10.3 |
CVE-2022-30580 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-41715 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-32189 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30635 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30633 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30632 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30631 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-30630 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-2880 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-2879 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-28131 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-27664 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-32148 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2022-1705 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2022-1962 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2022-41316 | Twistlock CVE | Medium | vault-1.10.3 |
CVE-2022-30629 | Twistlock CVE | Low | go-1.17.9 |
CVE-2022-41716 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-41717 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2021-4238 | Twistlock CVE | Critical | github.com/Masterminds/goutils-v1.1.0 |
CVE-2022-41723 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20220127200216-cd36cc0744dd |
CVE-2022-27664 | Twistlock CVE | High | golang.org/x/net-v0.0.0-20220127200216-cd36cc0744dd |
CVE-2022-27191 | Twistlock CVE | High | golang.org/x/crypto-v0.0.0-20220208050332-20e1d8d225ab |
CVE-2022-38149 | Twistlock CVE | High | github.com/hashicorp/consul-template-v0.28.1-0.20220415203157-ebf2f3dfe745 |
CVE-2022-29526 | Twistlock CVE | Medium | golang.org/x/sys-v0.0.0-20220207234003-57398862261d |
CVE-2023-24999 | Twistlock CVE | High | vault-1.10.3 |
CVE-2022-41725 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-41724 | Twistlock CVE | High | go-1.17.9 |
CVE-2022-41723 | Twistlock CVE | High | go-1.17.9 |
CVE-2023-24532 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2023-28840 | Twistlock CVE | High | github.com/docker/docker-v20.10.10 |
CVE-2023-28842 | Twistlock CVE | Medium | github.com/docker/docker-v20.10.10 |
CVE-2023-28841 | Twistlock CVE | Medium | github.com/docker/docker-v20.10.10 |
CVE-2023-0620 | Twistlock CVE | Medium | vault-1.10.3 |
CVE-2023-0665 | Twistlock CVE | Medium | vault-1.10.3 |
CVE-2023-25000 | Twistlock CVE | Medium | vault-1.10.3 |
CVE-2023-24537 | Twistlock CVE | High | go-1.17.9 |
CVE-2023-24538 | Twistlock CVE | Critical | go-1.17.9 |
CVE-2023-24536 | Twistlock CVE | High | go-1.17.9 |
CVE-2023-24534 | Twistlock CVE | High | go-1.17.9 |
PRISMA-2023-0056 | Twistlock CVE | Medium | github.com/sirupsen/logrus-v1.8.1 |
CVE-2023-24540 | Twistlock CVE | Critical | go-1.17.9 |
CVE-2023-29400 | Twistlock CVE | High | go-1.17.9 |
CVE-2023-24539 | Twistlock CVE | High | go-1.17.9 |
CVE-2023-34231 | Twistlock CVE | High | github.com/snowflakedb/gosnowflake-v1.6.3 |
CVE-2023-29405 | Twistlock CVE | Critical | go-1.17.9 |
CVE-2023-29404 | Twistlock CVE | Critical | go-1.17.9 |
CVE-2023-29402 | Twistlock CVE | Critical | go-1.17.9 |
CVE-2023-29403 | Twistlock CVE | High | go-1.17.9 |
CVE-2023-2121 | Twistlock CVE | Medium | vault-1.10.3 |
CVE-2023-29406 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2023-29409 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2022-28948 | Twistlock CVE | High | gopkg.in/yaml.v3-v3.0.0-20210107192922-496545a6307b |
CVE-2023-39319 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2023-39318 | Twistlock CVE | Medium | go-1.17.9 |
CVE-2023-5077 | Twistlock CVE | High | vault-1.10.3 |
CVE-2022-32149 | Twistlock CVE | High | golang.org/x/text-v0.3.7 |
CVE-2023-3978 | Twistlock CVE | Medium | golang.org/x/net-v0.0.0-20220127200216-cd36cc0744dd |
CVE-2023-39325 | Twistlock CVE | Medium | golang.org/x/net-v0.0.0-20220127200216-cd36cc0744dd |
CVE-2023-39323 | Twistlock CVE | Critical | go-1.17.9 |
CVE-2023-44487 | Twistlock CVE | Medium | golang.org/x/net-v0.0.0-20220127200216-cd36cc0744dd |
VAT: https://vat.dso.mil/vat/image?imageName=hashicorp/secure-secrets-management/vault-enterprise&tag=1.10.3&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=hashicorp/secure-secrets-management/vault-enterprise&tag=1.10.3&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.