[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110304151400.GJ24629@florz.florz.dyndns.org>
Date: Fri, 4 Mar 2011 16:14:00 +0100
From: Florian Zumbiehl <florz@...rz.de>
To: Solar Designer <solar@...nwall.com>
Cc: oss-security@...ts.openwall.com,
"Steven M. Christey" <coley@...us.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>
Subject: Re: CVE Request -- logrotate -- nine issues
Hi,
> The rest, as described, appear to rely on sysadmin error and to assume
> security properties that logrotate never advertised it had. Specifically,
> logrotate was never declared to be safe to use on untrusted directories,
> and it was an error for a sysadmin to make such an assumption.
>
> I don't mind logrotate being enhanced/hardened in this respect, but to
> call these vulnerabilities sounds like a stretch. Also, even if
> logrotate is hardened, it should not be declared to be safe to use on
> untrusted directories. It'd be better to explicitly state that it is
> not, to avoid this sort of confusion.
In which scenarios exactly logrotate is supposed to be safe to use is
mostly undefined.
However, it is currently a common setup (as in: what distributions do out
of the box) to have a daily logrotate cron job run as root that rotates
the logs of all the services and to have log directories owned by service
users (so they can create missing log files, for example).
In such setups, the service user can elevate its privileges to root
or corrupt root-owned files using the various bugs.
Florian
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.
