Re: Several memory safety violations in cpio 2.13

[Hanno Böck]

Did another check.

This sample
x3EwMDAwMDAwMDAwMDAwMDAwMDAAADAwMDA=
now causes a null pointer deref and segfault.

==31105==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 
0x55857f5e1f23 bp 0x000000000000 sp 0x7ffe483d2f30 T0)
==31105==The signal is caused by a READ memory access.
==31105==Hint: address points to the zero page.
    #0 0x55857f5e1f22 in read_name_from_file /tmp/cpio/src/copyin.c:1003
    #1 0x55857f5e1f22 in read_in_binary /tmp/cpio/src/copyin.c:1146
    #2 0x55857f5e3adb in read_in_header /tmp/cpio/src/copyin.c:989
    #3 0x55857f5e5a1f in process_copy_in /tmp/cpio/src/copyin.c:1285
    #4 0x55857f5cde62 in main /tmp/cpio/src/main.c:780
    #5 0x7f08bbd53f1a in __libc_start_main (/lib64/libc.so.6+0x23f1a)
    #6 0x55857f5cefd9 in _start (/tmp/c/cpio+0x13fd9)


-- 
Hanno Böck
https://hboeck.de/

mail/jabber: address@hidden
GPG: FE73757FA60E4E21B937579FA5880072BBB51E42