| Name | CVE-2017-1000382 |
| Description | VIM version 8.0.1187 (and other versions most likely) ignores umask when creating a swap file ("[ORIGINAL_FILENAME].swp") resulting in files that may be world readable or otherwise accessible in ways not intended by the user running the vi binary. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| vim (PTS) | jessie, jessie (lts) | 2:7.4.488-7+deb8u11 | vulnerable |
| stretch (security) | 2:8.0.0197-4+deb9u7 | vulnerable |
| stretch (lts), stretch | 2:8.0.0197-4+deb9u11 | vulnerable |
| buster (security), buster, buster (lts) | 2:8.1.0875-5+deb10u6 | vulnerable |
| bullseye | 2:8.2.2434-3+deb11u1 | vulnerable |
| bookworm | 2:9.0.1378-2 | vulnerable |
| sid, trixie | 2:9.1.0861-1 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|
| vim | source | (unstable) | (unfixed) | unimportant | | |
Notes
https://www.openwall.com/lists/oss-security/2017/10/31/15
Cf. https://www.openwall.com/lists/oss-security/2017/11/01/4
vim creates the .swp file according to the permissions of the file being
edited, admitely ignoring the umask, so in the reporters case the .swp
file is readable by others. But that seem to be the intended behaviour.