Bug 461745 - vim: arbitrary command execution when handling tar archives
vim: arbitrary command execution when handling tar archives
Status: CLOSED DUPLICATE of bug 451759
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
reported=20080808,public=20080808,sou...
: Security
Depends On:
Blocks: CVE-2008-2712
  Show dependency treegraph
 
Reported: 2008-09-10 08:18 EDT by Jan Lieskovsky
Modified: 2008-09-11 10:01 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-09-11 10:01:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2008-09-10 08:18:30 EDT
Description of problem:

A security vulnerability was discovered in the way, vim processes
the names of files, directories and tar archives. The fnameescape()
function makes the untrusted file name safe as an argument to ``execute''.
The sanitization of the provided inputs, performed by this function is not sufficient, which results into the situation,in which the code which uses the
output of the fnameescape() function is vulnerable again, i.e. the commands called by ``execute'' will in turn each interpret the untrusted file name
again. An attacker could use this flaw to execute arbitrary code when
handling tar archives.

Version-Release number of selected component (if applicable):
Vim >= 7.0 (possibly older)

How reproducible:
No reproducer

References:

    http://www.rdancer.org/vulnerablevim-tarplugin.v3.html (original report)

Proposed patch 7.2c.002

    http://groups.google.com/group/vim_dev/msg/80882b9ee9293139
    http://ftp.vim.org/pub/vim/unstable/patches/7.2c/7.2c.002
Comment 1 Jan Lieskovsky 2008-09-11 10:01:34 EDT

*** This bug has been marked as a duplicate of bug 451759 ***

Note You need to log in before you can comment on or make changes to this bug.