[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110304175214.GA26198@openwall.com>
Date: Fri, 4 Mar 2011 20:52:14 +0300
From: Solar Designer <solar@...nwall.com>
To: oss-security@...ts.openwall.com
Cc: Florian Zumbiehl <florz@...rz.de>,
"Steven M. Christey" <coley@...-smtp.mitre.org>,
Stefan Fritsch <sf@...itsch.de>, Jan Kaluza <jkaluza@...hat.com>,
Paul Martin <pm@...ian.org>, Petr Uzel <petr.uzel@...e.cz>,
Thomas Biege <thomas@...e.de>, Jan Lieskovsky <jlieskov@...hat.com>
Subject: Re: CVE Request -- logrotate -- nine issues
On Fri, Mar 04, 2011 at 12:05:02PM -0500, Steven M. Christey wrote:
>
> If there's a common usage scenario that doesn't stem from blatant
> administrator negligence, then a CVE is probably still appropriate.
> ("blatant admin negligence" might be, say, if an admin arbitrarily makes a
> script setuid, or modifies the perms for an executable or config file to
> be world-writable.)
I think that "chmod 777 /var/log" is "blatant admin negligence". As to,
say, "chown nginx /var/log/nginx", it could be negligence or it could be
lack of familiarity with the risks involved. So I am willing to admit
that it's not necessarily negligence that turns those issues into
vulnerabilities on specific systems.
> We will sometimes write the CVE description more as an "adminisrator
> practice" than as "fault of the software."
Oh, this is something I did not realize. A lot of people assume that
CVEs "blame" the software and its authors for having made an error.
It felt wrong, say, to blame a text editor for being unsafe to use on
files in untrusted directories when such unsafety was the typical and
expected situation for text editors in general.
Thank you for your responses!
Alexander
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.
