Not sure wether this applies to us: If a malicious local user has write access to a directory in which a target user is using unzip to extract a file to then a TOCTOU bug can be exploited to change the permission of any file belonging to that user. On decompressing unzip copies the permissions from the compressed file to the uncompressed file. However there is a gap between the uncompressed file being written (and it's file handler being close) and the permissions of the file being changed. During this gap a malicious user can remove the decompressed file and replace it with a hard-link to another file belonging to the user. unzip will then change the permissions on the hard-linked file to be the same as that of the compressed file. The vulnerable line of code can be found on line 1160 of the file unix.c where chmod is used (rather than fchmod). unzip also use's chmod in a number of other places which may also be vulnerable to exploitation.
Oh well what a nice bug number, let's close this as invalid and pretend nothing happened.
(In reply to comment #1) > Oh well what a nice bug number, let's close this as invalid and pretend > nothing happened. Hm, why? Doesn't look like the issue is fixed. Debian did in DSA 903-1 and issued a regression fix (DSA 903-2)
Carlo: we consider this is a ridiculous security issue, highly questionable whether we even consider this a bug, if the maintainer or upstream decides to fix it, that is fine, but we dont consider it worthy of attention from security team.
Hm, yes seems reasonable. Just wanted to be sure, this didn't got missed. Sorry for the noise.
