cve.bz

CVE-2017-17087 Exposure of Resource to Wrong Sphere

5.5 mediumEPSS 0.4%Fix available

Medium (5.5). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
fileio.c in Vim prior to 8.0.1263 sets the group ownership of a .swp file to the editor's primary group (which may be different from the group ownership of the original file), which allows local users to obtain sensitive information by leveraging an applicable group membership, as demonstrated by /etc/shadow owned by root:shadow mode 0640, but /etc/.shadow.swp owned by root:users mode 0640, a different vulnerability than CVE-2017-1000382.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-668 Exposure of Resource to Wrong Sphere
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-17087 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-17087?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-17087?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-17087 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
vim:vimbefore 8.0.1263
debian:debian_linux8.0
debian:debian_linux9.0
canonical:ubuntu_linux16.04
canonical:ubuntu_linux18.04

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian8vim2:7.4.488-7+deb8u4DLA-1871-1
Debian9vim2:8.0.0197-4+deb9u4DLA-2876-1
Debian12, 13, 14vim2:8.0.1401-1DEBIAN-CVE-2017-17087
Ubuntu16.04:LTSvim2:7.4.1689-3ubuntu1.5UBUNTU-CVE-2017-17087 USN-4582-1
Ubuntu18.04:LTSvim2:8.0.1453-1ubuntu1.4USN-4582-1
Ubuntu18.04:LTSvim2:8.0.1453-1ubuntu1.7USN-5147-1
Ubuntu20.04:LTSvim2:8.1.2269-1ubuntu5.4USN-5147-1
UbuntuPro:14.04:LTSvim2:7.4.052-1ubuntu3.1+esm4UBUNTU-CVE-2017-17087 USN-5147-1
UbuntuPro:16.04:LTSvim2:7.4.1689-3ubuntu1.5+esm3USN-5147-1
SUSEEnterprise Storage 6, Enterprise Storage 7, Linux Enterprise High Performance Computing 15 SP1-ESPOS and 22 morevim8.2.5038-150000.5.21.1SUSE-SU-2022:2102-1
SUSELinux Enterprise Server 12 SP2-BCL, Linux Enterprise Server 12 SP3-BCL, Linux Enterprise Server 12 SP4-LTSS and 5 morevim9.0.0814-17.9.1SUSE-SU-2022:4619-1
openSUSELeap 15.3, Leap 15.4vim8.2.5038-150000.5.21.1SUSE-SU-2022:2102-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 5vimWill not fix
Red Hat Enterprise Linux 6vimWill not fix
Red Hat Enterprise Linux 7vimWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2017-17087.

References

Check your stackJSON