GNU bug report logs -
#72283
Path traversal in gzip's -S option
Previous Next
Reported by: Alex Stumpf <gnu <at> AlexStumpf.de>
Date: Thu, 25 Jul 2024 00:40:01 UTC
Severity: normal
Done: Paul Eggert <eggert <at> cs.ucla.edu>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Hi,
I just stumbled upon a "feature" that was probably not intended with the
-S parameter:
$ cat /tmp/importantfile
important content
$ gzip -f -k -S .d/../../tmp/importantfile /etc/ld.so.conf
$ cat /tmp/importantfile
<gzipped content of /etc/ld.so.conf>
$
I.e., it is possible to create/overwrite files at arbitrary locations
(provided the user has write permission) just by using gzip parameters.
This is not an issue for systems with regular shell access, but e.g.
someone who sets up a restricted shell or allows execution of gzip via a
web interface might not expect that behavior.
The command works because there is both an /etc/ld.so.conf file as well
as an /etc/ld.so.conf.d/ directory. So the resulting filename
/etc/ld.so.conf.d/../../tmp/importantfile is a valid path.
It's up to you whether you consider this a fix-worthy bug, but I think
it wouldn't hurt to test whether compressed and uncompressed files are
in the same directory.
Cheers
Alex
This bug report was last modified 352 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.