Skip to content
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

Tracer panic for ICMP TimeExceeded packets with code 1 ("Fragment reassembly time exceeded") #979

Closed
fujiapple852 opened this issue Feb 3, 2024 · 0 comments · Fixed by #980
Labels
bug Something isn't working
Milestone

Comments

@fujiapple852
Copy link
Owner

Tracer crashes when processing an IMCP TimeExceeded with a code of 1 ("Fragment reassembly time exceeded")

For sufficiently long packets, the tracer will incorrectly interpret the TE payload (the fragmented packet) as an ICMP extension and crash with a message similar to:

thread 'tracer-31398' panicked at src/tracing/packet/icmp_extension.rs:426:33:
range end index 713 out of range for slice of length 416

The fix is to filter out ICMP TimeExceeded packets where the code != 0 ("TTL expired in transit.")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant