Skip to content

x/exp/trace, internal/trace/v2: malformed trace causes index out of range #64879

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.

Sign up for GitHub

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

Jump to bottom
Closed
dominikh opened this issue Dec 27, 2023 · 1 comment
Closed

x/exp/trace, internal/trace/v2: malformed trace causes index out of range #64879

dominikh opened this issue Dec 27, 2023 · 1 comment
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Go1.22

Comments

@dominikh
Copy link
Member

Running go tool trace -d=1 on the attached file, which contains []byte("go 1.22 trace\x00\x00\x00\x01000\x85\x00\b0001"), panics. The same is true for using x/exp/trace.

$ go tool trace -d=1 crash.trace 
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
internal/trace/v2.(*Reader).ReadEvent(0xc000206000)
	/home/dominikh/prj/go/src/internal/trace/v2/reader.go:160 +0xc38
cmd/trace/v2.debugProcessedEvents({0xc20aa0?, 0xc0000b2960?})
	/home/dominikh/prj/go/src/cmd/trace/v2/main.go:166 +0xf8
cmd/trace/v2.Main({0x7fffc2753a9a?, 0xc0000222b0?}, {0x8c5dcb, 0xb}, {0xc00010fe10?, 0x7fa1ac?}, 0x1)
	/home/dominikh/prj/go/src/cmd/trace/v2/main.go:34 +0x11f8
main.main()
	/home/dominikh/prj/go/src/cmd/trace/main.go:87 +0xa4e

crash.trace.gz

/cc @mknyszek
@gopherbot gopherbot added this to the Unreleased milestone Dec 27, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/552995 mentions this issue: internal/trace/v2: avoid several panics for malformed traces

@thanm thanm added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Dec 27, 2023
@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Jan 12, 2024
@dmitshur dmitshur modified the milestones: Unreleased, Go1.22 Jan 12, 2024
ezz-no pushed a commit to ezz-no/go-ezzno that referenced this issue Feb 18, 2024
@dominikh @ezz-no
internal/trace/v2: avoid several panics for malformed traces
cb6e9fd 
This addresses some panics (out of bounds slice accesses and nil pointer
dereferences) when parsing malformed data. These were found via light
fuzzing, not by any rigorous means, and more potential panics probably
exist.

Fixes golang#64878.
Fixes golang#64879.

Change-Id: I4085788ba7dc91fec62e4abd88f50777577db42f
Reviewed-on: https://go-review.googlesource.com/c/go/+/552995
Auto-Submit: Michael Knyszek <mknyszek@google.com>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
@golang golang locked and limited conversation to collaborators Jan 11, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Go1.22
Development

No branches or pull requests
4 participants
@dominikh @dmitshur @gopherbot @thanm