From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Xulei (Stone)" <stone.xulei@huawei.com>
Cc: "Ian.Jackson" <Ian.Jackson@eu.citrix.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] oss-security - CVE-2014-3672 libvirt: DoS via excessive logging
Date: Thu, 21 Jul 2016 09:55:35 +0100 [thread overview]
Message-ID: <20160721085535.GA13528@redhat.com> (raw)
In-Reply-To: <8E78D212B8C25246BE4CE7EA0E645FE53D7ED8@SZXEMI504-MBS.china.huawei.com>
On Thu, Jul 21, 2016 at 02:24:43AM +0000, Xulei (Stone) wrote:
> Hi,
>
> A CVE（CVE-2014-3672） vulnerability was reported in Xen.
> I want to know how to reproduce this CVE and whether the qemu-kvm was affected ?
>
> Hyperlink: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3672
> Hyperlink: http://www.openwall.com/lists/oss-security/2016/05/24/5
Yes, QEMU is affected, but we did not fix it at the QEMU layer. Instead
libvirt has introduced a virtlogd daemon to handle all writing of data
to files. So QEMU now merely writes a pipe FD, and virtlogd takes care
of file rotation.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2016-07-21 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 2:24 [Qemu-devel] oss-security - CVE-2014-3672 libvirt: DoS via excessive logging Xulei (Stone)
2016-07-21 8:55 ` Daniel P. Berrange [this message]
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=20160721085535.GA13528@redhat.com \
--to=berrange@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=stone.xulei@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.