[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YSQ.7.76.1711221200110.4822@wniryva>
Date: Wed, 22 Nov 2017 12:13:23 +0530 (IST)
From: P J P <ppandit@...hat.com>
To: oss security list <oss-security@...ts.openwall.com>
Subject: Re: Re: CVE-2017-16845 Qemu: ps2: information leakage
via post_load routine
Hello Ian,
+-- On Tue, 21 Nov 2017, Ian Zimmerman wrote --+
| > -> https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg02982.html
|
| Hi, what can I do with these QEMU reports? I can try to apply the
| patch, but I have no idea if it will work, because I don't know which
| branch or revision it is based on.
Patch is sent against upstream Qemu git repository(below) and is merged
after due review on the -devel list.
-> https://git.qemu.org/?p=qemu.git;a=summary
| By my unscientific counting, there are only 2 other userspace projects which
| earn CVEs as frequently as QEMU: openjpeg and graphicsmagick. In both these
| cases, starting with the message posted here and following the references, I
| can quickly locate the actual VC commit (in git and mercurial, respectively)
| and thus have a sound basis for deciding what to do: patch, wait for an
| updated distro package, or fork the distro package.
|
| Is there a reason why that cannot be done with QEMU?
Reviewed patches soon show-up in the above master repository. In this case, it
so happened that an earlier version v1 of the patch was more acceptable
-> https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg02946.html
It should make it upstream soon, I'll update here accordingly.
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
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.
