-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Golang vulnerabilities in v0.13.1 #324
Comments
In addition, Trivy scanner identifies vulnerabilities in: golang.org/x/net golang.org/x/text Thanks |
This has been addressed by the bot in #344 and #347
This one should be solved by 2794ee0 |
@hc-github-team-es-release-engineering Since #344 and #347 have been merged. Can we get a new release of envcosul with these fixes? |
I agree with @marrws ,we need a new release including the security fixes |
|
@armon @catsby @ryanuber @hc-github-team-es-release-engineering I'm really sorry for the ping but this is important. Can we get a new release so the vulnerabilities don't keep piling up? |
Thanks for reporting. Closing duplicated issue to centralize conversation/updates in this issue #362 and this PR #366. A fix should be available on the next release. For future reporting of vulnerabilities, we recommend reaching to the [email protected] email to have faster replies as described in our guide https://www.hashicorp.com/trust/security/vulnerability-management. |
Envconsul version
envconsul v0.13.1
CVE Vulnerabilities
Here is a list of Golang vulnerabilities that can be fixed by doing a version upgrade of the package:
The text was updated successfully, but these errors were encountered: