We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@rolandshoemaker requested issue #69138 to be considered for backport to the next 1.23 minor release.
@gopherbot please open backport issues for this security fix.
The text was updated successfully, but these errors were encountered:
Change https://go.dev/cl/611175 mentions this issue: [release-branch.go1.23] go/parser: track depth in nested element lists
[release-branch.go1.23] go/parser: track depth in nested element lists
Sorry, something went wrong.
Closed by merging CL 611175 (commit 53487e5) to release-branch.go1.23.
release-branch.go1.23
53487e5
Prevents stack exhaustion with extremely deeply nested literal values, i.e. field values in structs. Updates #69138 Fixes #69143 Fixes CVE-2024-34155 Change-Id: I2e8e33b44105cc169d7ed1ae83fb56df0c10f1ee Reviewed-on: https://go-internal-review.googlesource.com/c/go/+/1520 Reviewed-by: Robert Griesemer <gri@google.com> Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Russ Cox <rsc@google.com> (cherry picked from commit eb1b038c0d01761694e7a735ef87ac9164c6568e) Reviewed-on: https://go-internal-review.googlesource.com/c/go/+/1560 Commit-Queue: Roland Shoemaker <bracewell@google.com> Reviewed-by: Tatiana Bradley <tatianabradley@google.com> Reviewed-on: https://go-review.googlesource.com/c/go/+/611175 Auto-Submit: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Bypass: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Michael Pratt <mpratt@google.com>
No branches or pull requests
@rolandshoemaker requested issue #69138 to be considered for backport to the next 1.23 minor release.
The text was updated successfully, but these errors were encountered: