-
Notifications
You must be signed in to change notification settings - Fork 64
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
[Spike] Check if we need to explicitly disable HTTP/2 to mitigate CVE-2023-44487
(Rapid Reset)
#1315
Comments
CVE-2023-44487
(Rapid Reset vuln)
CVE-2023-44487
(Rapid Reset vuln)CVE-2023-44487
(Rapid Reset)
CVE-2023-44487
(Rapid Reset)CVE-2023-44487
(Rapid Reset)
The results of this investigation work have been shared in a doc titled TL;DR And from my research, there seems to be currently only one repo where we need to do so:
I'm marking this issue as done and will create a follow-up issue to make the necessary changes in The steps for disabling the HTTP/2 protocol in /close EDIT: #1342 created |
@rm3l: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind task
As part of #1303, we'll need to bump a few of our dependencies across several repos.
But even doing so might not be sufficient to mitigate the HTTP/2 Rapid Reset vuln (CVE-2023-44487).
The scope of this issue is to check whether we also need to explicitly disable HTTP/2 as an additional safety measure.
If the answer is yes, we'll need to create follow-up issues.
The text was updated successfully, but these errors were encountered: