Fix Wireshark crash when following TCP stream with JA4 plugin #257
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
igr001-galactica
approved these changes
Oct 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #256
This PR fixes a crash that occurred in the Wireshark GUI when using Follow -> TCP Stream with the JA4 plugin installed.
Root cause:
display_hashes_from_packet_table()could attempt to add fields under an invalid or incomplete subtree. When the GUI later traversed this subtree (e.g. during stream follow), Wireshark crashed.Verification:
wireshark -r http1.pcapng-> no crash on Follow TCP Streamtshark(it doesn’t access GUI display-tree paths)