Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 1508786 - (CVE-2017-1000382) CVE-2017-1000382 vim: Ignores umask when creating a swap file
CVE-2017-1000382 vim: Ignores umask when creating a swap file
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20171031,reported=2...
: Security
Depends On: 1508787
Blocks: 1508790
  Show dependency tree / graph
 
Reported: 2017-11-02 04:54 EDT by Andrej Nemec
Modified: 2018-02-12 03:58 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
It was found that vim applies the opened file read permissions to the swap file, overriding the process' umask. An attacker might search for vim swap files that were not deleted properly, in order to retrieve sensible data.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-20 05:36:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Andrej Nemec 2017-11-02 04:54:02 EDT 
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.

References:

http://seclists.org/oss-sec/2017/q4/145
Comment 1 Andrej Nemec 2017-11-02 04:54:29 EDT 
Created vim tracking bugs for this issue:

Affects: fedora-all [bug 1508787]
Comment 3 Cedric Buissart 2017-12-20 05:36:22 EST 
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/.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.