-
Notifications
You must be signed in to change notification settings - Fork 1
chore(deps): update rust crate h2 to v0.3.26 [security] #184
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1875bc2
to
3a376b8
Compare
This was referenced May 8, 2024
Depends on stackabletech/h2#3 |
@nightkr This now has conflicts |
The conflict should be sorted out, and this should now be R4R. Tests pass against K8s 1.25.16. |
NickLarsenNZ
previously approved these changes
May 13, 2024
NickLarsenNZ
approved these changes
May 13, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
=0.3.18
->=0.3.26
=0.3.18
->=0.3.26
GitHub Vulnerability Alerts
GHSA-8r5v-vm4m-4g25
An attacker with an HTTP/2 connection to an affected endpoint can send a steady stream of invalid frames to force the
generation of reset frames on the victim endpoint.
By closing their recv window, the attacker could then force these resets to be queued in an unbounded fashion,
resulting in Out Of Memory (OOM) and high CPU usage.
This fix is corrected in hyperium/h2#737, which limits the total number of
internal error resets emitted by default before the connection is closed.
GHSA-q6cp-qfwq-4gcv
An attacker can send a flood of CONTINUATION frames, causing
h2
to process them indefinitely. This results in an increase in CPU usage.Tokio task budget helps prevent this from a complete denial-of-service, as the server can still respond to legitimate requests, albeit with increased latency.
More details at https://seanmonstar.com/blog/hyper-http2-continuation-flood/.
Patches available for 0.4.x and 0.3.x versions.
Release Notes
hyperium/h2 (h2)
v0.3.26
Compare Source
What's Changed
See https://seanmonstar.com/blog/hyper-http2-continuation-flood/ for more info.
v0.3.25
Compare Source
What's Changed
Full Changelog: hyperium/h2@v0.3.24...v0.3.25
v0.3.24
Compare Source
Fixed
v0.3.23
Compare Source
What's Changed
v0.3.22
Compare Source
header_table_size(usize)
option to client and server builders.v0.3.21
Compare Source
RecvStream
to return data even if it has received aCANCEL
stream error.v0.3.20
Compare Source
:status
pseudo header in the 1xx range.v0.3.19
Compare Source
too_many_resets
in opaque debug data of GOAWAY when too many resets received.Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Berlin, 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.