From: "G. Campana" <gcampana+kvm@quarkslab.com>
To: Will.Deacon@arm.com
Cc: kvm@vger.kernel.org, andre.przywara@arm.com, gcampana+kvm@quarkslab.com
Subject: [PATCH 0/5] [PATCH v2] kvmtool: fix virtio 9p vulnerabilities
Date: Thu, 10 Nov 2016 16:21:06 +0100 [thread overview]
Message-ID: <1478791271-7558-1-git-send-email-gcampana+kvm@quarkslab.com> (raw)
This patch series should fix different vulnerabilities found in virtio 9p
(http://www.spinics.net/lists/kvm/msg130505.html), but it definitely needs some
testing. By the way, the very same path traversal vulnerability was also found
in Qemu in August: http://www.openwall.com/lists/oss-security/2016/08/30/1
and the path traversal fix looks quite similar.
v2:
* merge some commits
* add an explicit commit message to each patch
* add a Signed-off-by: line
v1:
G. Campana (5):
kvmtool: 9p: fix path traversal vulnerabilities
kvmtool: 9p: fix sprintf vulnerabilities
kvmtool: 9p: fix strcpy vulnerabilities
kvmtool: 9p: refactor fixes with get_full_path()
kvmtool: 9p: fix a buffer overflow in rel_to_abs
virtio/9p.c | 199 +++++++++++++++++++++++++++++++++++++++++++++++-------------
1 file changed, 158 insertions(+), 41 deletions(-)
--
2.7.4
next reply other threads:[~2016-11-10 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 15:21 G. Campana [this message]
2016-11-10 15:21 ` [PATCH 1/5] kvmtool: 9p: fix path traversal vulnerabilities G. Campana
2016-11-10 15:21 ` [PATCH 2/5] kvmtool: 9p: fix sprintf vulnerabilities G. Campana
2016-11-10 15:21 ` [PATCH 3/5] kvmtool: 9p: fix strcpy vulnerabilities G. Campana
2016-11-10 15:21 ` [PATCH 4/5] kvmtool: 9p: refactor fixes with get_full_path() G. Campana
2016-11-10 15:21 ` [PATCH 5/5] kvmtool: 9p: fix a buffer overflow in rel_to_abs G. Campana
2016-11-18 17:55 ` [PATCH 0/5] [PATCH v2] kvmtool: fix virtio 9p vulnerabilities Will Deacon
2016-11-21 10:25 ` G. Campana
2016-11-21 10:33 ` Andre Przywara
2016-11-21 10:48 ` [PATCH 0/5] [PATCH v2] kvmtool: 9p: fix regression introduced by previous patch G. Campana
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=1478791271-7558-1-git-send-email-gcampana+kvm@quarkslab.com \
--to=gcampana+kvm@quarkslab.com \
--cc=Will.Deacon@arm.com \
--cc=andre.przywara@arm.com \
--cc=kvm@vger.kernel.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 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.