-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
internal/zstd: avoid panic when windowSize is negative #63979
Labels
Milestone
Comments
aimuz
added a commit
to aimuz/go
that referenced
this issue
Nov 7, 2023
Consistency of Window_Size and Frame_Content_Size value ranges as per RFC 8878 3.1.1.1.2 to resolve panic issues. Fixes golang#63979
Change https://go.dev/cl/540415 mentions this issue: |
aimuz
added a commit
to aimuz/go
that referenced
this issue
Nov 9, 2023
Consistency of Window_Size and Frame_Content_Size value ranges as per RFC 8878 3.1.1.1.2 to resolve panic issues. Fixes golang#63979
aimuz
added a commit
to aimuz/go
that referenced
this issue
Nov 9, 2023
Consistency of Window_Size and Frame_Content_Size value ranges as per RFC 8878 3.1.1.1.2 to resolve panic issues. Fixes golang#63979
aimuz
added a commit
to aimuz/go
that referenced
this issue
Nov 11, 2023
Consistency of Window_Size and Frame_Content_Size value ranges as per RFC 8878 3.1.1.1.2 to resolve panic issues. Fixes golang#63979
aimuz
added a commit
to aimuz/go
that referenced
this issue
Nov 12, 2023
Consistency of Window_Size and Frame_Content_Size value ranges as per RFC 8878 3.1.1.1.2 to resolve panic issues. Fixes golang#63979
aimuz
added a commit
to aimuz/go
that referenced
this issue
Nov 18, 2023
Consistency of Window_Size and Frame_Content_Size value ranges as per RFC 8878 3.1.1.1.2 to resolve panic issues. Fixes golang#63979
ezz-no
pushed a commit
to ezz-no/go-ezzno
that referenced
this issue
Feb 18, 2024
This change fixes an edge case in the zstd decompressor where an int conversion could result in a negative window size. Fixes golang#63979 For golang#62513 Change-Id: Ie714bf8fb51fa509b310deb8bd2c96bd87b52852 GitHub-Last-Rev: ab0be65 GitHub-Pull-Request: golang#63980 Reviewed-on: https://go-review.googlesource.com/c/go/+/540415 Reviewed-by: Cherry Mui <cherryyz@google.com> Run-TryBot: M Zhuo <mengzhuo1203@gmail.com> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: M Zhuo <mengzhuo1203@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What did you do?
Window_Size should have the same value range as Frame_Content_Size, when Frame_Content_Size exceeds the maximum value of int64, it will cause Window_Size to become negative.
According to RFC 8878, Frame_Content_Size can be any value from 1 to 2^64-1 bytes (16 EB).
Testing with the following values will trigger this issue, resulting in a panic
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: