[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <807f9c58-ee87-c594-ea89-be816ac6d2ae@redhat.com>
Date: Fri, 22 Jan 2021 05:37:22 -0500
From: Daniel Walsh <dwalsh@...hat.com>
To: oss-security@...ts.openwall.com
Subject: Re: CVE-2020-35517 QEMU: virtiofsd: potential
privileged host device access from guest
On 1/22/21 03:12, P J P wrote:
> Hello,
>
> A potential host privilege escalation issue was found in the virtio-fs
> shared file system daemon (virtiofsd) of the QEMU. Virtio-fs daemon
> shares host directory tree with a guest VM. The said privilege
> escalation scenario may occur if a privileged guest user was to create
> device special file in the shared directory and use it to r/w access
> host devices. A privileged guest user may use this flaw to arbitrarily
> access (r/w) host files resulting in DoS scenario or may potentially
> escalate privileges on the host.
>
> Upstream patch:
> ---------------
> -> https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg05461.html
>
> * This issue was reported by Alex Xu (CC'd).
>
> * 'CVE-2020-35517' assigned by Red Hat Inc.
>
> Thank you.
> --
> Prasad J Pandit / Red Hat Product Security Team
> 8685 545E B54C 486B C6EB 271E E285 8B5A F050 DE8D
>
Did SELinux block this flaw? Seems virtiofsd should be running without
CAP_MKNOD by default.
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.
