From: "Andreas Färber" <afaerber@suse.de>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH stable-1.1] qga: set umask 0077 when daemonizing (CVE-2013-2007)
Date: Mon, 27 May 2013 02:19:23 +0200 [thread overview]
Message-ID: <51A2A68B.9090703@suse.de> (raw)
In-Reply-To: <51A2A4B6.2030400@redhat.com>
Am 27.05.2013 02:11, schrieb Laszlo Ersek:
> On 05/26/13 15:34, Andreas Färber wrote:
>> From: Laszlo Ersek <lersek@redhat.com>
>>
>> The qemu guest agent creates a bunch of files with insecure permissions
>> when started in daemon mode. For example:
>>
>> -rw-rw-rw- 1 root root /var/log/qemu-ga.log
>> -rw-rw-rw- 1 root root /var/run/qga.state
>> -rw-rw-rw- 1 root root /var/log/qga-fsfreeze-hook.log
>>
>> In addition, at least all files created with the "guest-file-open" QMP
>> command, and all files created with shell output redirection (or
>> otherwise) by utilities invoked by the fsfreeze hook script are affected.
>>
>> For now mask all file mode bits for "group" and "others" in
>> become_daemon().
>>
>> Temporarily, for compatibility reasons, stick with the 0666 file-mode in
>> case of files newly created by the "guest-file-open" QMP call. Do so
>> without changing the umask temporarily.
>>
>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
>> (cherry picked from commit c689b4f1bac352dcfd6ecb9a1d45337de0f1de67)
>>
>> [AF: Use error_set() instead of error_setg*()]
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> ---
>> qemu-ga.c | 2 +-
>> qga/commands-posix.c | 117 +++++++++++++++++++++++++++++++++++++++++++++++++--
>> 2 files changed, 115 insertions(+), 4 deletions(-)
[...]
> Looks good to me.
>
> Do you plan to backport
>
> 8fe6bbc qga: distinguish binary modes in "guest_file_open_modes" map
> 2b72001 qga: unlink just created guest-file if fchmod() or fdopen()
> fails on it
>
> too? These are considered polish for the CVE fix.
I did backport both to openSUSE 12.2 - they apply without conflicts. :)
I mainly posted this one to check if there are better QERRs to use.
> Also, a side-note: existing world-writable log files etc. are not
> recreated nor have their modes changed, so maybe a release note or some
> such would be useful for admins ("delete your previous logfile &
> optional unix domain socket, or change their modes manually").
Feel free to add a note to the 1.5 Release Notes - it can then be copied
to the previous releases we backport this fix to.
Apart from 1.1 I backported to our 1.3 branch.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-05-27 0:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 13:34 [Qemu-devel] [PATCH stable-1.1] qga: set umask 0077 when daemonizing (CVE-2013-2007) Andreas Färber
2013-05-27 0:11 ` Laszlo Ersek
2013-05-27 0:12 ` Laszlo Ersek
2013-05-27 0:19 ` Andreas Färber [this message]
2013-05-27 0:28 ` Laszlo Ersek
2013-05-27 18:33 ` Laszlo Ersek
2013-05-31 18:48 ` Anthony Liguori
2013-06-04 13:59 ` Andreas Färber
2013-06-04 14:23 ` Anthony Liguori
2013-06-05 8:33 ` [Qemu-devel] [Qemu-stable] " Michael Tokarev
2013-06-05 12:43 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51A2A68B.9090703@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).