0.28.0

Update module golang.org/x/net to v0.17.0 [SECURITY] @renovate (#86)

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
golang.org/x/net	v0.8.0 -> v0.17.0

GitHub Vulnerability Alerts

CVE-2023-3978

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.

CVE-2023-39325

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.

CVE-2023-44487

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.

---

0.27.1

Auto release fix @goruha (#93)

What

• Use auto relesase shared workflow

Why

• https://cloudposse.atlassian.net/browse/DEV-1747

v0.27.0

Update goreleaser/goreleaser-action action to v5 @renovate (#84)

This PR contains the following updates:

Package	Type	Update	Change
goreleaser/goreleaser-action	action	major	v4 -> v5

---

Release Notes

goreleaser/goreleaser-action (goreleaser/goreleaser-action)

v5

Compare Source

---

v0.26.0

Update docker/setup-buildx-action action to v3 @renovate (#88)

This PR contains the following updates:

Package	Type	Update	Change
docker/setup-buildx-action	action	major	v2 -> v3

---

Release Notes

docker/setup-buildx-action (docker/setup-buildx-action)

v3

Compare Source

---

v0.25.0

Update docker/login-action action to v3 @renovate (#87)

This PR contains the following updates:

Package	Type	Update	Change
docker/login-action	action	major	v2 -> v3

---

Release Notes

docker/login-action (docker/login-action)

v3

Compare Source

---

v0.24.0

Update docker/setup-qemu-action action to v3 @renovate (#91)

This PR contains the following updates:

Package	Type	Update	Change
docker/setup-qemu-action	action	major	v2 -> v3

---

Release Notes

docker/setup-qemu-action (docker/setup-qemu-action)

v3

Compare Source

---

v0.23.0

Update actions/setup-go action to v5 @renovate (#90)

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-go	action	major	v3 -> v5

---

Release Notes

actions/setup-go (actions/setup-go)

v5

Compare Source

v4

Compare Source

---

v0.22.0

Update docker/build-push-action action to v5 @renovate (#85)

This PR contains the following updates:

Package	Type	Update	Change
docker/build-push-action	action	major	v3 -> v5

---

Release Notes

docker/build-push-action (docker/build-push-action)

v5

Compare Source

v4

Compare Source

---

v0.21.0

Update actions/checkout action to v4 @renovate (#82)

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	v3 -> v4

---

Release Notes

actions/checkout (actions/checkout)

v4

Compare Source

• Support fetching without the --progress option
• Update to node20

---

v0.20.0

Update module github.com/google/go-github/v50 to v50.2.0 @renovate (#73)

This PR contains the following updates:

Package	Type	Update	Change
github.com/google/go-github/v50	require	minor	v50.1.0 -> v50.2.0

---

Release Notes

google/go-github (github.com/google/go-github/v50)

v50.2.0

Compare Source

This minor release contains the following interesting changes:

• Add ListExternalGroupsForTeamBySlug to Teams API (#​2674)
• Add DicussionCommentEvent Webhook (#​2678)
• Add head_sha for ListWorkflowRunsOptions (#​2703)
• Support HTTP Proxy from environment (#​2686)
• Update custom repo roles URL (#​2702)
• Move to Protonmail PGP (#​2666)
• Fix SCIM query params (#​2680)
• Add fields to update repository API and create branch protection API to match GitHub APIs (#​2709)

in addition to these more maintenance-type changes:

• Bump golang.org/x/sys from 0.0.0-20210615035016-665e8c7367d1 to 0.1.0 in /example (#​2676)
• Bump github.com/xlzd/gotp from 0.0.0-20181030022105-c8557ba2c119 to 0.1.0 in /scrape (#​2684)
• Update golangci-lint-action (#​2694)
• Bump github.com/google/go-github/v50 from 50.0.0 to 50.1.0 in /scrape (#​2683)
• Bump golang.org/x/crypto from 0.0.0-20210817164053-32db794688a5 to 0.1.0 in /example (#​2689)
• Bump golang.org/x/net from 0.0.0-20210226172049-e18ecbb05110 to 0.7.0 in /example (#​2691)
• Bump golang.org/x/net from 0.0.0-20210226172049-e18ecbb05110 to 0.7.0 (#​2692)
• Run go mod tidy -compat=1.17 (#​2696)
• Fix golangci-lint (#​2697)
• Bump golang.org/x/crypto from 0.0.0-20210817164053-32db794688a5 to 0.7.0 (#​2693)
• Bump golang.org/x/oauth2 from 0.0.0-20180821212333-d2e6202438be to 0.6.0 (#​2695)
• Remove example subdirs in GitHub Actions linter workflow (#​2701)
• Bump golang.org/x/net from 0.7.0 to 0.8.0 in /scrape (#​2698)
• Bump version of go-github to v50.2.0 (#​2710)

---

Consolidate auto-release workflow @goruha (#89)

what

• Use cloudposse/github-action-auto-release in auto-release.yaml workflow

why

• Solve old nodejs warning
• Reduce duplication of code