Bug#1028409: vim: insecure use of /var/tmp when editing .gz files

2023-01-13 Thread Bram Moolenaar
> On Tue, Jan 10, 2023 at 06:58:15PM +0100, Jakub Wilk wrote: > > If you edit a foo.gz file from a directory which is not writable by you, Vim > > tries to use /var/tmp/foo.gz.swp as the swap file, > > Vim prefers to use ~/tmp/foo.gz.swp, but it won't create ~/tmp for you. This reminds me that

Bug#1028409: vim: insecure use of /var/tmp when editing .gz files

2023-01-12 Thread James McCoy
On Tue, Jan 10, 2023 at 06:58:15PM +0100, Jakub Wilk wrote: > If you edit a foo.gz file from a directory which is not writable by you, Vim > tries to use /var/tmp/foo.gz.swp as the swap file, Vim prefers to use ~/tmp/foo.gz.swp, but it won't create ~/tmp for you. As for why this is happening

Bug#1028409: vim: insecure use of /var/tmp when editing .gz files

2023-01-10 Thread Jakub Wilk
Package: vim Version: 2:9.0.1000-3 Tags: security If you edit a foo.gz file from a directory which is not writable by you, Vim tries to use /var/tmp/foo.gz.swp as the swap file, even when this file already exist and is owned by somebody else. This can be exploited for denial of service, maybe