Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 10 Jul 2008 18:55:46 +0200
From: Tomas Hoger <>
        Jonathan Smith
Cc:, Bram Moolenaar <>,
        "Charles E
 Campbell, Jr" <>,
        Jan Minar <>
Subject: Re: Re: More arbitrary code executions in Netrw
 version 125, Vim 7.2a.10

Hi Jonathan!

On Tue, 8 Jul 2008 13:53:48 -0400 (EDT) "Steven M. Christey"
<> wrote:

> On Mon, 7 Jul 2008, Jonathan Smith wrote:
> > Steve, could we get CVEs assigned, please? I'd imagine we'd need
> > three; one for the tarplugin issue, one for the zipplugin, and one
> > for the netrw issues (which are similar enough to probably justify
> > lumping them together).
> CVE-2008-3074 - tarplugin
> CVE-2008-3075 - zipplugin
> CVE-2008-3076 - netrw issues
> These will be filled in later.

Are you sure 3 new CVEs are needed for this second rdancer advisory?
Advisory text itself only speaks of netrw issues and it's not quite
obvious to me why zip and tar tests are included in the test suite.
Maybe just to point out that those issues are still unfixed.

Moreover, if you diff zipplugin directories in vulnerablevim.tar.bz2
and vulnerablevim-netrw.tar.bz2, you will see this test did not change
at all between the two test suites.  So CVE-2008-3075 should already
be covered by previous CVE-2008-2712.

tarplugin test was updated since the first test suite to use different
payload.  I'm not really sure if it is the same issue or not, but the
new exploit is blocked by the previously proposed Jan's patch.  So it
may be the same issue as described in the first advisory.  Btw,
CVE-2008-2712 description does not mention tar.vim issue.  It is
described in, but its test does not seem to be run when doing
make test for the top-most Makefile in the first test suite.

Jonathan, did new netrw tests work for you?  With which vim version?
They all failed for me with vim 7.1.245 / netrw 109.

Adding also Jan to CC, in case he is interested in tossing in some
comments.  For some context for discussion, you can see:

Jan, feel free to ignore this discussion if you are not interested,
though your comments are welcome.


Tomas Hoger

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.