Source: https://code.google.com/p/google-security-research/issues/detail?id=643 The following crash due to a stack-based out-of-bounds read can be observed in an ASAN build of Wireshark (current git master), by feeding a malformed file to tshark ("$ ./tshark -nVxr /path/to/file"): --- cut --- ==3901==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7ffeadbc852d at pc 0x0000009cea23 bp 0x7ffeadbbf650 sp 0x7ffeadbbf648 READ of size 1 at 0x7ffeadbc852d thread T0 #0 0x9cea22 in find_signature wireshark/wiretap/vwr.c:2214:17 #1 0x9c5066 in vwr_read_s2_s3_W_rec wireshark/wiretap/vwr.c:1435:15 #2 0x9bc02a in vwr_process_rec_data wireshark/wiretap/vwr.c:2336:20 #3 0x9babf2 in vwr_read wireshark/wiretap/vwr.c:653:10 #4 0x9d64c2 in wtap_read wireshark/wiretap/wtap.c:1314:7 #5 0x535c1a in load_cap_file wireshark/tshark.c:3479:12 #6 0x52c1df in main wireshark/tshark.c:2197:13 Address 0x7ffeadbc852d is located in stack of thread T0 at offset 32813 in frame #0 0x9bbbcf in vwr_process_rec_data wireshark/wiretap/vwr.c:2320 This frame has 1 object(s): [32, 32800) 'rec' <== Memory access at offset 32813 overflows this variable HINT: this may be a false positive if your program uses some custom stack unwind mechanism or swapcontext (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-buffer-overflow wireshark/wiretap/vwr.c:2214:17 in find_signature Shadow bytes around the buggy address: 0x100055b71050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100055b71060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100055b71070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100055b71080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100055b71090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x100055b710a0: 00 00 00 00 f3[f3]f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 0x100055b710b0: f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 0x100055b710c0: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 0x100055b710d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100055b710e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x100055b710f0: f1 f1 f1 f1 04 f2 04 f3 00 00 00 00 00 00 00 00 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Container overflow: fc Array cookie: ac Intra object redzone: bb ASan internal: fe Left alloca redzone: ca Right alloca redzone: cb ==3901==ABORTING --- cut --- The crash was reported at https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11791. Attached are two files which trigger the crash. Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/39004.zip