-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
chore(deps): update actions/checkout action to v4.1.7 - autoclosed #42
Conversation
Important Auto Review SkippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
🔍 Vulnerabilities of
|
digest | sha256:acaace99eeaca213f35f8fabeb7974b4d176e9a47e67451fa63c3add30833c2a |
vulnerabilities | |
size | 126 MB |
packages | 240 |
📦 Base Image php:8.1-alpine
golang.org/x/net
|
Affected range | <0.17.0 |
Fixed version | 0.17.0 |
CVSS Score | 7.5 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
EPSS Score | 0.21% |
EPSS Percentile | 59th percentile |
Description
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.
google.golang.org/grpc 1.54.0
(golang)
pkg:golang/google.golang.org/[email protected]
Affected range | <1.56.3 |
Fixed version | 1.56.3 |
CVSS Score | 7.5 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Description
Impact
In affected releases of gRPC-Go, it is possible for an attacker to send HTTP/2 requests, cancel them, and send subsequent requests, which is valid by the HTTP/2 protocol, but would cause the gRPC-Go server to launch more concurrent method handlers than the configured maximum stream limit.
Patches
This vulnerability was addressed by #6703 and has been included in patch releases: 1.56.3, 1.57.1, 1.58.3. It is also included in the latest release, 1.59.0.
Along with applying the patch, users should also ensure they are using the
grpc.MaxConcurrentStreams
server option to apply a limit to the server's resources used for any single connection.Workarounds
None.
References
#6703
🔍 Vulnerabilities of
|
digest | sha256:7035ddfe5cb7e1904d96402ca036973e1d8e4a5c8924842e83c897956a65388b |
vulnerabilities | |
size | 97 MB |
packages | 203 |
📦 Base Image php:8-alpine
golang.org/x/net
|
Affected range | <0.17.0 |
Fixed version | 0.17.0 |
CVSS Score | 7.5 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
EPSS Score | 0.21% |
EPSS Percentile | 59th percentile |
Description
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.
google.golang.org/grpc 1.54.0
(golang)
pkg:golang/google.golang.org/[email protected]
Affected range | <1.56.3 |
Fixed version | 1.56.3 |
CVSS Score | 7.5 |
CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Description
Impact
In affected releases of gRPC-Go, it is possible for an attacker to send HTTP/2 requests, cancel them, and send subsequent requests, which is valid by the HTTP/2 protocol, but would cause the gRPC-Go server to launch more concurrent method handlers than the configured maximum stream limit.
Patches
This vulnerability was addressed by #6703 and has been included in patch releases: 1.56.3, 1.57.1, 1.58.3. It is also included in the latest release, 1.59.0.
Along with applying the patch, users should also ensure they are using the
grpc.MaxConcurrentStreams
server option to apply a limit to the server's resources used for any single connection.Workarounds
None.
References
#6703
Recommended fixes for image
|
Name | 8.3.6-alpine3.19 |
Digest | sha256:dc7d4d8248ec8c31bfa65ec964b7db7b34384cf9a3a16ee5fbc8bf25e29c7413 |
Vulnerabilities | |
Pushed | 3 weeks ago |
Size | 38 MB |
Packages | 49 |
Flavor | alpine |
OS | 3.19 |
Runtime | 8.3.6 |
The base image is also available under the supported tag(s):8-alpine3.19
,8-cli-alpine
,8-cli-alpine3.19
,8.3-alpine
,8.3-alpine3.19
,8.3-cli-alpine
,8.3-cli-alpine3.19
,8.3.6-alpine
,8.3.6-alpine3.19
,8.3.6-cli-alpine
,8.3.6-cli-alpine3.19
,alpine
,alpine3.19
,cli-alpine
,cli-alpine3.19
Refresh base image
Rebuild the image using a newer base image version. Updating this may result in breaking changes.✅ This image version is up to date.
Change base image
✅ There are no tag recommendations at this time.
5697e63
to
9f9affb
Compare
9f9affb
to
d33781b
Compare
d33781b
to
8755f88
Compare
8755f88
to
92f79ae
Compare
Pull request was closed
This PR contains the following updates:
v4.1.4
->v4.1.7
Release Notes
actions/checkout (actions/checkout)
v4.1.7
Compare Source
v4.1.6
Compare Source
v4.1.5
Compare Source
What's Changed
user.email
to be41898282+github-actions[bot]@​users.noreply.github.com
by @cory-miller in https://github.com/actions/checkout/pull/1707Full Changelog: actions/checkout@v4.1.4...v4.1.5
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.