Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 07 Jun 2011 07:19:14 +0800
From: Eugene Teo <>
CC: Jan Lieskovsky <>,
        "Steven M. Christey" <>,
        Chris Evans <>, Greg KH <>,
        Kees Cook <>
Subject: Re: CVE Request -- vsftpd -- Do not create network
 namespace per connection

On 06/07/2011 12:19 AM, Jan Lieskovsky wrote:
> Hello, Josh, Steve, vendors,
>   It was found that vsftpd, Very Secure FTP daemon, when the network
> namespace (CONFIG_NET_NS) support was activated in the kernel, used to
> create a new network namespace per connection. A remote attacker could
> use this flaw to cause a memory pressure and denial of the vsftpd
> service.
> References:
> [1]
> [2]
> [3]
> This one being a bit tricky one -- from my understanding of the issue,
> vsftpd doesn't necessarily have a security flaw on its side. It's
> kernel issue / bug, which allows this to be used for vsftpd DoS:
> [4]
> [5]
> Short-term solution would be probably to address this on the vsftpd
> side, the long-term one then being to get this fixed in kernel.
> Though not sure, how it would be wrt to CVE identifier(s) assignment.
> Steve, could you advice here?

It is worth noting that for a local, unprivileged user to trigger this,
they will need to have the CAP_SYS_ADMIN capability. So this limits the
attack to some services like vsftpd. I see this more of a kernel issue
as configuring vsftpd to set isolate_network=NO is not a long-term solution.

Thanks, Eugene

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.