Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C064D9D.7000308@redhat.com>
Date: Wed, 02 Jun 2010 14:25:01 +0200
From: Jan Lieskovsky <jlieskov@...hat.com>
To: oss-security@...ts.openwall.com
CC: "Steven M. Christey" <coley@...us.mitre.org>,
        Panu Matilainen <pmatilai@...hat.com>,
        Jindrich Novy <jnovy@...hat.com>, Florian Festi <ffesti@...hat.com>,
        Matt McCutchen <matt@...tmccutchen.net>
Subject: Re: CVE Request -- rpm -- Fails to remove the SUID/SGID
 bits on package upgrade (RH BZ#598775)

Steve,

Jan Lieskovsky wrote:
> Hi Steve, vendors,
> 
>    Matt McCutchen pointed out a deficiency in the way rpm handled rpm 
> package upgrades --
> it failed to clear out the SUID/SGID bits of the old file by file 
> replacement when privileged
> user performed package upgrade. Under certain circumstances, a local, 
> authenticated user could
> use this flaw to escalate their privileges.

Maybe obvious and natural conclusion from previous post already, but Panu clarified
yet, similar deficiency holds for dealing with posix file capabilities and SELinux
contexts, i.e. they are not cleared after pkg upgrade. Not sure second CVE is needed
for this, but if one is enough, wanted to explicitly mention this, so it can be
described in the text of the CVE too.

Thanks && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Response Team

> 
> Red Hat Bugzilla entry:
>   [1] https://bugzilla.redhat.com/show_bug.cgi?id=598775
> 
> Upstream changeset:
>   [2] 
> http://rpm.org/gitweb?p=rpm.git;a=commit;h=ca2d6b2b484f1501eafdde02e1688409340d2383 
> 
> 
> Could you allocate CVE id for this?
> 
> Thanks && Regards, Jan.
> -- 
> Jan iankko Lieskovsky / Red Hat Security Response Team

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.