-
Notifications
You must be signed in to change notification settings - Fork 688
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
SEGV bug in pkg/server/fsm.go
#2725
Comments
You use two GoBGP daemons? |
No, only the under-test node uses the GoBGP daemon. |
What BGP daemon other side? |
The other side is a fuzzer that continuously generates BGP packets and sends them to the under-test node for testing. @fujita |
CVE-2023-46565 was assigned to this issue. |
Hello together, I looked into the code and found a possible reason for the segv message (unfortunate I do not have time to test the pcap stream against a fixed version to confirm my assumptions), anyway here are my thoughts: The function (h *fsmHandler) recvMessageWithError() calls What do you think about it, does this make sense? |
I triggered a SEGV bug when fuzzing gobgp.
The config of the under-test node is as follows, and its IP is
10.0.255.6
The fuzzing node is deployed on
10.0.255.5
.The log snippet around the crash point:
The full logs and network capture are as attached.
SEGV_debugMode.log
SEGV_network_capture.pcap.zip
The text was updated successfully, but these errors were encountered: