On Thursday, September 28, 2017 at 4:45:57 AM UTC+3, Tony Mechelynck wrote:
> On Thu, Sep 28, 2017 at 2:39 AM, James McCoy <[email protected]> wrote:
> > On Wed, Sep 27, 2017 at 03:04:00PM -0700, Gary Johnson wrote:
> [...]
> >> An attacker, requiring no special permissions,
> >
> > Except the ability to put arbitrary files on your computer. If someone
> > can get arbitrary content onto your system, then you've already lost.
> >
> > The "vulnerability" here is that the user put a untrusted file into a
> > location that Vim executes. That has nothing to do with Vim and
> > everything to do with the user.
>
> Indeed. There are, or used to be, some «games» or other «software
> packages» whose mode of operation was to send you by email an
> executable binary. As long as the content was legit, and did what it
> was supposed to do, and nothing else, that was OK. But how could the
> user tell that the program was not, let's say, «leaking» to some
> spammer a copy of the entire user's address book while said user was
> blissfully playing some thrilling game with a friend over the
> Internet? So the word came to be circulated: Never execute a binary
> that you got by email.
>
> With Vim plugins, at least, the «payload» is a source file (for the
> Vim interpreter) and it is not overly difficult to find out what that
> plugin actually does (though I admit it does require some technical
> knowledge, but the latter can be had from Vim's excellent online help
> system). If some starry-eyed user runs some untrusted «plugin» without
> checking anything, gets hurt, then comes to Bram or to any of us
> crying Mommy, what can we do?
>
> Best regards,
> Tony.
Hi,
Thanks all for the replies.
Bottom line - I agree with Heptite and Tony that this problem is a single
example in a big category, and can be reproduced with other applications as
well. I am convinced by the comments that this is not a pure Vim issue, though
a step can still be taken to help users protect from this abuse.
For example, Notepad++ on Windows does not load user plugins (located in
AppData) when run as Administrator - unless an Administrator explicitly puts a
specific file in the protected installation directory
("allowAppDataPlugins.xml").
Best,
Dor Azouri
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.