From: Greg Kurz <groug@kaod.org>
To: P J P <ppandit@redhat.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Felix Wilhelm <fwilhelm@ernw.de>,
"Michael S. Tsirkin" <mtsirkin@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] About a virtio 9p backend issue
Date: Wed, 10 Aug 2016 19:54:11 +0200 [thread overview]
Message-ID: <20160810195411.0c3b3ef8@kaod.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1608102026130.11543@wniryva>
Le Wed, 10 Aug 2016 20:28:27 +0530 (IST),
P J P <ppandit@redhat.com> a écrit :
> +-- On Wed, 10 Aug 2016, Greg Kurz wrote --+
> | As Michael already pointed in a previous mail, this will break legal paths
> | with a component ending in ".." like "foo../bar". The fix should only ban
> | paths containing a component that is strictly equal to "..".
>
> But that would not fix the path traversal issue, would it? As in, one could
> traverse the path like foo/bar/../../bar1 ?
>
Unless I've missed something, if you forbid all paths containing at least one
".." component, the path traversal issue is fixed, isn't it ? Something like
strstr(path, "/../") or paths starting with "../" or ending with "/.." ?
I don't expect the official linux driver to pass relative paths to QEMU, but
I cannot check this out. I guess you should verify that it is still possible
to use relative paths in the guest.
And what about the other backends, especially the proxy one ?
Also I realize this thread is private: please Cc qemu-devel when sending
your patch and don't forget to add appropriate Signed-off-by tags, as it
is mandatory for acceptance.
Thanks for chasing this issue. I think it's been there for a long time but
it would be great to have this fixed in 2.7.
Cheers.
--
Greg
> Thank you.
> --
> Prasad J Pandit / Red Hat Product Security Team
> 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
parent reply other threads:[~2016-08-10 17:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.LFD.2.20.1608102026130.11543@wniryva>]
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=20160810195411.0c3b3ef8@kaod.org \
--to=groug@kaod.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=fwilhelm@ernw.de \
--cc=mtsirkin@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@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).