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

security(deps): update 🛡️ golang.org/x/net to v0.23.0 [security] #117

Merged
merged 1 commit into from
Jul 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 14, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
golang.org/x/net v0.17.0 -> v0.23.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2023-45288

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.


net/http, x/net/http2: close connections when receiving too many headers

BIT-golang-2023-45288 / CVE-2023-45288 / GHSA-4v7x-pqxf-cx7m / GO-2024-2687

More information

Details

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


HTTP/2 CONTINUATION flood in net/http

BIT-golang-2023-45288 / CVE-2023-45288 / GHSA-4v7x-pqxf-cx7m / GO-2024-2687

More information

Details

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

The fix sets a limit on the amount of excess header frames we will process before closing a connection.

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner April 14, 2024 12:00
@renovate renovate bot added the security label Apr 14, 2024
@renovate renovate bot requested a review from andrii-zakurenyi April 14, 2024 12:00
@renovate renovate bot enabled auto-merge (squash) April 14, 2024 12:00
renovate-approve[bot]
renovate-approve bot previously approved these changes Apr 14, 2024
@renovate renovate bot changed the title security(deps): update 🛡️ golang.org/x/net to v0.23.0 [security] security(deps): update 🛡️ golang.org/x/net to v0.23.0 [security] - autoclosed Apr 18, 2024
@renovate renovate bot closed this Apr 18, 2024
auto-merge was automatically disabled April 18, 2024 18:37

Pull request was closed

@renovate renovate bot deleted the renovate/go-golang.org/x/net-vulnerability branch April 18, 2024 18:37
@renovate renovate bot changed the title security(deps): update 🛡️ golang.org/x/net to v0.23.0 [security] - autoclosed security(deps): update 🛡️ golang.org/x/net to v0.23.0 [security] Apr 21, 2024
@renovate renovate bot restored the renovate/go-golang.org/x/net-vulnerability branch April 21, 2024 08:33
@renovate renovate bot reopened this Apr 21, 2024
@renovate renovate bot force-pushed the renovate/go-golang.org/x/net-vulnerability branch from 65f9ce0 to e600ba3 Compare April 21, 2024 08:33
@renovate renovate bot enabled auto-merge (squash) April 21, 2024 08:33
Copy link
Contributor Author

renovate bot commented Jun 8, 2024

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 2 additional dependencies were updated

Details:

Package Change
golang.org/x/sys v0.15.0 -> v0.18.0
golang.org/x/term v0.15.0 -> v0.18.0

@renovate renovate bot force-pushed the renovate/go-golang.org/x/net-vulnerability branch from e600ba3 to 13f5f31 Compare June 8, 2024 00:34
@renovate renovate bot force-pushed the renovate/go-golang.org/x/net-vulnerability branch 4 times, most recently from 01af8fc to ca57d56 Compare June 11, 2024 21:01
@sheldonhull sheldonhull removed the request for review from andrii-zakurenyi July 16, 2024 20:19
@renovate renovate bot force-pushed the renovate/go-golang.org/x/net-vulnerability branch from cd166a7 to 85a9836 Compare July 18, 2024 01:49
@renovate renovate bot force-pushed the renovate/go-golang.org/x/net-vulnerability branch from 85a9836 to 47e1955 Compare July 18, 2024 01:54
@renovate renovate bot merged commit 98c77e7 into main Jul 18, 2024
9 checks passed
@renovate renovate bot deleted the renovate/go-golang.org/x/net-vulnerability branch July 18, 2024 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants