summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/none/1736376
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/none/1736376')
-rw-r--r--results/classifier/zero-shot/108/none/173637631
1 files changed, 31 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/none/1736376 b/results/classifier/zero-shot/108/none/1736376
new file mode 100644
index 000000000..66e288644
--- /dev/null
+++ b/results/classifier/zero-shot/108/none/1736376
@@ -0,0 +1,31 @@
+device: 0.522
+graphic: 0.481
+semantic: 0.478
+network: 0.462
+files: 0.416
+vnc: 0.368
+other: 0.334
+socket: 0.326
+performance: 0.263
+PID: 0.255
+boot: 0.240
+permissions: 0.211
+debug: 0.172
+KVM: 0.024
+
+CVE-2017-7471 repeated?
+
+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);
+}
+
+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.
+
+