https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16375
--- Comment #2 from Peter Wu <pe...@lekensteyn.nl> ---
Created attachment 17718
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17718&action=edit
Packet capture file
I fixed https://github.com/Lekensteyn/wireshark-fuzztools and generated the
packet capture based on the reproducer.
To reproduce the crash, a two-pass dissection is required:
tshark -2r
clusterfuzz-testcase-fuzzshark_udp_port-dhcp-5658761805168640.pcap
To create the pcap from the original binary reproducer, this command can be
used:
oss-fuzz-report.py --proto udp_port-dhcp
clusterfuzz-testcase-fuzzshark_udp_port-dhcp-5658761805168640 20585 --memleaks
If you do not have a reproducer yet and just the oss-fuzz issue ID like I did
initially, I followed these steps to download a capture and try to reproduce
the issue:
1. Follow the Setup instructons from the wireshark-fuzztools README
2. Log in to https://oss-fuzz.com/, this may require special permissions.
3. Log in to https://bugs.chromium.org/p/oss-fuzz
4. Obtain the SACSID and session cookies, store it in /tmp/mc (see README)
5. Run: grab-monorail.py -c /tmp/mc 20585 --memleaks
Usually it can be reproduced with fuzzshark, but as this seems to require a
two-pass dissection, it did not work:
FUZZSHARK_TARGET=dhcp fuzzshark
clusterfuzz-testcase-fuzzshark_udp_port-dhcp-5658761805168640
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
