Skip to content
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

Backport of [NET-8946 NET-8947 NET-8948] security: bump go, x/net and envoy versions into release/1.3.x #477

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #474 to be assessed for backporting due to the inclusion of the label backport/1.3.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@zalimeni
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-dataplane/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


Description
Upgrade to use Go 1.21.9. This resolves CVEs
CVE-2023-45288 (http2).

Upgrade to support Envoy 1.28.2. This resolves CVEs
CVE-2024-27919 (http2).

Upgrade to use golang.org/x/net v0.24.0. This resolves CVEs
CVE-2023-45288 (x/net).

Checklist
Tests added
CHANGELOG entry added


Overview of commits

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

Copy link

hashicorp-cla-app bot commented Apr 11, 2024

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


2 out of 3 committers have signed the CLA.

  • zalimeni
  • dduzgun-security
  • temp

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@dduzgun-security dduzgun-security marked this pull request as ready for review April 12, 2024 17:16
@dduzgun-security dduzgun-security requested a review from a team as a code owner April 12, 2024 17:16
Copy link
Member

@zalimeni zalimeni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor fix, otherwise LGTM

.changelog/477.txt Outdated Show resolved Hide resolved
@zalimeni zalimeni enabled auto-merge (squash) April 16, 2024 20:26
@zalimeni zalimeni merged commit f285763 into release/1.3.x Apr 16, 2024
29 of 30 checks passed
@zalimeni zalimeni deleted the backport/security/net-8946-8947-8948/largely-pleasant-jawfish branch April 16, 2024 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants