When using the proxy backend, all accesses to the host filesystem are
handled by an external process running in a chroot() jail. No need to
bother about paths in this case.
CVE-2017-7471 is only applicable to the local backend, because accesses
are handled by QEMU directly in this case.
** Changed in: qemu
Status: New => Invalid
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-7471
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1736376
Title:
CVE-2017-7471 repeated?
Status in QEMU:
Invalid
Bug description:
In the hw/9pfs/9p-proxy.c file I can see the following which is
changed because of CVE-2017-7471 in the hw/9pfs/9p-local.c. I might be
wrong but I guess that should be changed as well.
if(dir_path){
v9fs_path_sprintf(target,"%s/%s",dir_path->data,name);
}
else{
v9fs_path_sprintf(target,"%s",name);
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1736376/+subscriptions
