Closed
Description
Calling any of the Parse functions on Go source code which contains deeply nested types or declarations can cause a panic due to stack exhaustion.
Thanks to Juho Nurminen of Mattermost for reporting this issue.
This is CVE-2022-1962.
(This was a PRIVATE issue tracked in http://b/236145171 and fixed by http://tg/1491025.)
/cc https://github.com/orgs/golang/teams/security and https://github.com/orgs/golang/teams/release
Metadata
Metadata
Assignees
Type
Projects
Status
Done
Relationships
Development
No branches or pull requests
Activity
tatianab commentedon Jul 6, 2022
@gopherbot please open backport issues for this security fix
gopherbot commentedon Jul 6, 2022
Backport issue(s) opened: #53707 (for 1.17), #53708 (for 1.18).
Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases.
gopherbot commentedon Jul 12, 2022
Change https://go.dev/cl/417056 mentions this issue:
[release-branch.go1.18] go/parser: limit recursion depth
gopherbot commentedon Jul 12, 2022
Change https://go.dev/cl/417063 mentions this issue:
go/parser: limit recursion depth
gopherbot commentedon Jul 12, 2022
Change https://go.dev/cl/417070 mentions this issue:
[release-branch.go1.17] go/parser: limit recursion depth
[release-branch.go1.18] go/parser: limit recursion depth
11 remaining items