See how unarr compares to other vendors in security performance
unarr through 1.1.1 contains a heap-based out-of-bounds read in zipparseextrafields() in zip/parse-zip.c due to an incorrect ZIP64 extra field length check. Attackers can supply a crafted ZIP archive with 0xFFFFFFFF sentinel values and a truncated ZIP64 record to read past the heap buffer and crash the process.
unarr through 1.1.1 contains an off-by-one heap-based buffer overflow in targetname() in tar/parse-tar.c, reachable through the arentrygetname() API. Attackers can supply a crafted TAR archive with a full ustar prefix and name to write a NUL byte past the allocation, corrupting heap memory and crashing the process.