First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 238120
Alias:
Product:
Component:
Status: NEW
Resolution:
Assigned To: Gentoo Security <security@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Robert Buchholz <rbu@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:
Flags: Requestee:
 
 
  ()

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 238120 depends on: Show dependency tree
Show dependency graph
Bug 238120 blocks:

Additional Comments: (this is where you put emerge --info)









View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-09-19 15:19 0000
CVE-2008-4101 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-4101):
  Vim 3.0 through 7.x before 7.2.010 does not properly escape
  characters, which allows user-assisted attackers to (1) execute
  arbitrary shell commands by entering a K keystroke on a line that
  contains a ";" (semicolon) followed by a command, or execute
  arbitrary Ex commands by entering an argument after a (2) "Ctrl-]"
  (control close-square-bracket) or (3) "g]" (g close-square-bracket)
  keystroke sequence, a different issue than CVE-2008-2712.

------- Comment #1 From Robert Buchholz 2008-09-19 15:55:35 0000 -------
I am not able to reproduce this issue, vim herd?

------- Comment #2 From Elias Pipping 2008-09-19 18:12:43 0000 -------
Steps to reproduce:

Open a new file in vim.
Type in http://www.google.co.uk/search?q=&xclock&.
Press V (capital), thereby selecting the whole line in visual mode.
Press K (capital), thereby looking up the selection.

As a result, xclock is launched.

------- Comment #3 From Ali Polatel 2008-09-19 18:55:22 0000 -------
{gvim,vim,vim-core}-7.2.021 are in CVS.

------- Comment #4 From Tobias Heinlein 2008-09-21 11:41:26 0000 -------
Given that I'm running 7.2.021 and am still able to reproduce it as described
in comment #2, I assume not all issues are fixed?

------- Comment #5 From Elias Pipping 2008-10-10 17:58:07 0000 -------
(In reply to comment #4)
> Given that I'm running 7.2.021 and am still able to reproduce it as described
> in comment #2, I assume not all issues are fixed?
> 
That doesn't surprise me much. There might be something I'm missing about the
way vim is built
in gentoo, but it looks like the fix (patch 7.2.010) is never applied. Not only
because I can't seem
to find it anywhere among the patches that actually are applied, but also
because I can happily cd
to $S and apply the patch myself.

First Last Prev Next    No search results available      Search page      Enter new bug