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

fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) - autoclosed #41

Closed

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 9, 2023

Mend Renovate

This PR contains the following updates:

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

Improper rendering of text nodes in golang.org/x/net/html

CVE-2023-3978 / GHSA-2wrh-6pvc-2jm9 / GO-2023-1988

More information

Details

Text nodes not in the HTML namespace are incorrectly literally rendered, causing text which should be escaped to not be. This could lead to an XSS attack.

Severity

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

References

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


Improper rendering of text nodes in golang.org/x/net/html

CVE-2023-3978 / GHSA-2wrh-6pvc-2jm9 / GO-2023-1988

More information

Details

Text nodes not in the HTML namespace are incorrectly literally rendered, causing text which should be escaped to not be. This could lead to an XSS attack.

Severity

Unknown

References

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


HTTP/2 Stream Cancellation Attack

BIT-apisix-2023-44487 / BIT-aspnet-core-2023-44487 / BIT-contour-2023-44487 / BIT-dotnet-2023-44487 / BIT-dotnet-sdk-2023-44487 / BIT-envoy-2023-44487 / BIT-golang-2023-44487 / BIT-jenkins-2023-44487 / BIT-kong-2023-44487 / BIT-nginx-2023-44487 / BIT-nginx-ingress-controller-2023-44487 / BIT-node-2023-44487 / BIT-solr-2023-44487 / BIT-tomcat-2023-44487 / BIT-varnish-2023-44487 / CVE-2023-44487 / GHSA-2m7v-gc89-fjqf / GHSA-qppj-fm5r-hxr3 / GHSA-vx74-f528-fxqg / GHSA-xpw8-rcwv-8f8p

More information

Details

HTTP/2 Rapid reset attack

The HTTP/2 protocol allows clients to indicate to the server that a previous stream should be canceled by sending a RST_STREAM frame. The protocol does not require the client and server to coordinate the cancellation in any way, the client may do it unilaterally. The client may also assume that the cancellation will take effect immediately when the server receives the RST_STREAM frame, before any other data from that TCP connection is processed.

Abuse of this feature is called a Rapid Reset attack because it relies on the ability for an endpoint to send a RST_STREAM frame immediately after sending a request frame, which makes the other endpoint start working and then rapidly resets the request. The request is canceled, but leaves the HTTP/2 connection open.

The HTTP/2 Rapid Reset attack built on this capability is simple: The client opens a large number of streams at once as in the standard HTTP/2 attack, but rather than waiting for a response to each request stream from the server or proxy, the client cancels each request immediately.

The ability to reset streams immediately allows each connection to have an indefinite number of requests in flight. By explicitly canceling the requests, the attacker never exceeds the limit on the number of concurrent open streams. The number of in-flight requests is no longer dependent on the round-trip time (RTT), but only on the available network bandwidth.

In a typical HTTP/2 server implementation, the server will still have to do significant amounts of work for canceled requests, such as allocating new stream data structures, parsing the query and doing header decompression, and mapping the URL to a resource. For reverse proxy implementations, the request may be proxied to the backend server before the RST_STREAM frame is processed. The client on the other hand paid almost no costs for sending the requests. This creates an exploitable cost asymmetry between the server and the client.

Multiple software artifacts implementing HTTP/2 are affected. This advisory was originally ingested from the swift-nio-http2 repo advisory and their original conent follows.

swift-nio-http2 specific advisory

swift-nio-http2 is vulnerable to a denial-of-service vulnerability in which a malicious client can create and then reset a large number of HTTP/2 streams in a short period of time. This causes swift-nio-http2 to commit to a large amount of expensive work which it then throws away, including creating entirely new Channels to serve the traffic. This can easily overwhelm an EventLoop and prevent it from making forward progress.

swift-nio-http2 1.28 contains a remediation for this issue that applies reset counter using a sliding window. This constrains the number of stream resets that may occur in a given window of time. Clients violating this limit will have their connections torn down. This allows clients to continue to cancel streams for legitimate reasons, while constraining malicious actors.

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 rapid reset can cause excessive work in net/http

BIT-golang-2023-39325 / CVE-2023-39325 / GHSA-4374-p667-p6c8 / GO-2023-2102

More information

Details

A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

Severity

Unknown

References

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


HTTP/2 rapid reset can cause excessive work in net/http

BIT-golang-2023-39325 / CVE-2023-39325 / GHSA-4374-p667-p6c8 / GO-2023-2102

More information

Details

A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

Severity

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

References

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


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 changed the title fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) - autoclosed Oct 9, 2023
@renovate renovate bot closed this Oct 9, 2023
@renovate renovate bot deleted the deps-update/main-go-golang.org/x/net-vulnerability branch October 9, 2023 22:32
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) - autoclosed fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) Oct 10, 2023
@renovate renovate bot reopened this Oct 10, 2023
@renovate renovate bot restored the deps-update/main-go-golang.org/x/net-vulnerability branch October 10, 2023 01:12
@renovate renovate bot force-pushed the deps-update/main-go-golang.org/x/net-vulnerability branch from 19765e3 to c4c05d1 Compare October 10, 2023 01:15
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) - autoclosed Oct 10, 2023
@renovate renovate bot closed this Oct 10, 2023
@renovate renovate bot deleted the deps-update/main-go-golang.org/x/net-vulnerability branch October 10, 2023 06:58
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) - autoclosed fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) Oct 10, 2023
@renovate renovate bot reopened this Oct 10, 2023
@renovate renovate bot restored the deps-update/main-go-golang.org/x/net-vulnerability branch October 10, 2023 14:06
@renovate renovate bot force-pushed the deps-update/main-go-golang.org/x/net-vulnerability branch from c4c05d1 to a55d861 Compare October 10, 2023 14:10
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) - autoclosed Oct 10, 2023
@renovate renovate bot closed this Oct 10, 2023
@renovate renovate bot deleted the deps-update/main-go-golang.org/x/net-vulnerability branch October 10, 2023 15:51
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) - autoclosed fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) Oct 10, 2023
@renovate renovate bot reopened this Oct 10, 2023
@renovate renovate bot restored the deps-update/main-go-golang.org/x/net-vulnerability branch October 10, 2023 21:20
@renovate renovate bot force-pushed the deps-update/main-go-golang.org/x/net-vulnerability branch from a55d861 to 072d8bd Compare October 10, 2023 21:25
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) - autoclosed Oct 11, 2023
@renovate renovate bot closed this Oct 11, 2023
@renovate renovate bot deleted the deps-update/main-go-golang.org/x/net-vulnerability branch October 11, 2023 00:42
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) - autoclosed fix(deps): update module golang.org/x/net to v0.13.0 [security] (main) Oct 11, 2023
@renovate renovate bot reopened this Oct 11, 2023
@renovate renovate bot restored the deps-update/main-go-golang.org/x/net-vulnerability branch October 11, 2023 22:24
@renovate renovate bot force-pushed the deps-update/main-go-golang.org/x/net-vulnerability branch from 072d8bd to 17f9752 Compare October 11, 2023 22:27
@renovate renovate bot deleted the deps-update/main-go-golang.org/x/net-vulnerability branch January 22, 2024 15:24
@renovate renovate bot restored the deps-update/main-go-golang.org/x/net-vulnerability branch January 25, 2024 07:26
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) - autoclosed fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) Jan 25, 2024
@renovate renovate bot reopened this Jan 25, 2024
@renovate renovate bot force-pushed the deps-update/main-go-golang.org/x/net-vulnerability branch from 58c1c87 to 6104a8a Compare January 25, 2024 07:30
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) - autoclosed Jan 25, 2024
@renovate renovate bot closed this Jan 25, 2024
@renovate renovate bot deleted the deps-update/main-go-golang.org/x/net-vulnerability branch January 25, 2024 12:40
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) - autoclosed fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) Jan 26, 2024
@renovate renovate bot reopened this Jan 26, 2024
@renovate renovate bot restored the deps-update/main-go-golang.org/x/net-vulnerability branch January 26, 2024 00:34
@renovate renovate bot force-pushed the deps-update/main-go-golang.org/x/net-vulnerability branch from 6104a8a to ea1333d Compare January 26, 2024 00:41
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) - autoclosed Jan 26, 2024
@renovate renovate bot closed this Jan 26, 2024
@renovate renovate bot deleted the deps-update/main-go-golang.org/x/net-vulnerability branch January 26, 2024 14:47
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) - autoclosed fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) Jan 26, 2024
@renovate renovate bot reopened this Jan 26, 2024
@renovate renovate bot restored the deps-update/main-go-golang.org/x/net-vulnerability branch January 26, 2024 17:35
@renovate renovate bot force-pushed the deps-update/main-go-golang.org/x/net-vulnerability branch from ea1333d to 58c0dc8 Compare January 26, 2024 17:42
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) - autoclosed Jan 26, 2024
@renovate renovate bot closed this Jan 26, 2024
@renovate renovate bot deleted the deps-update/main-go-golang.org/x/net-vulnerability branch January 26, 2024 19:31
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) - autoclosed fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) Jan 26, 2024
@renovate renovate bot restored the deps-update/main-go-golang.org/x/net-vulnerability branch January 26, 2024 21:40
@renovate renovate bot reopened this Jan 26, 2024
@renovate renovate bot force-pushed the deps-update/main-go-golang.org/x/net-vulnerability branch from 58c0dc8 to ecd735a Compare January 26, 2024 21:46
@renovate renovate bot changed the title fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) fix(deps): update module golang.org/x/net to v0.17.0 [security] (main) - autoclosed Jan 27, 2024
@renovate renovate bot closed this Jan 27, 2024
@renovate renovate bot deleted the deps-update/main-go-golang.org/x/net-vulnerability branch January 27, 2024 01:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants