Re: Several memory safety violations in cpio 2.13

[Sergey Poznyakoff]

Hanno Böck <address@hidden> ha escrit:

> No, this was from a fresh git checkout.

Weird.

1. Running your example on a fresh git checkout:

 src/cpio/tmp$ echo 'x3EwMDAwMKIwMDAwMDAwMDAwMDAKAAAAAAAwMDAwMDAwMDAA' | \
               base64 -d | ../src/cpio -i
 ../src/cpio: Substituting `.' for empty hard link target
 ../src/cpio: premature end of file

2. The same with valgrind

 src/cpio/tmp$ echo 'x3EwMDAwMKIwMDAwMDAwMDAwMDAKAAAAAAAwMDAwMDAwMDAA' | \
               base64 -d | valgrind ../src/cpio -i
 
==1543== Memcheck, a memory error detector
==1543== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1543== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright
info
==1543== Command: ../src/cpio -i
==1543==
../src/cpio: 000000000 not created: newer or same age version exists
../src/cpio: premature end of file
==1543==
==1543== HEAP SUMMARY:
==1543==     in use at exit: 1,664 bytes in 3 blocks
==1543==   total heap usage: 106 allocs, 103 frees, 15,490 bytes
allocated
==1543==
==1543== LEAK SUMMARY:
==1543==    definitely lost: 0 bytes in 0 blocks
==1543==    indirectly lost: 0 bytes in 0 blocks
==1543==      possibly lost: 0 bytes in 0 blocks
==1543==    still reachable: 1,664 bytes in 3 blocks
==1543==         suppressed: 0 bytes in 0 blocks
==1543== Rerun with --leak-check=full to see details of leaked memory
==1543==
==1543== For counts of detected and suppressed errors, rerun with: -v
==1543== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Regards,
Sergey