Vserver vulnerabilities
6 vulnerabilities
Known vulnerabilities in Vserver products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 2 products.
Products
2- Linux Vserver4 vulnerabilities
- Util Vserver2 vulnerabilities
CVE-2003-1288vserverlinux-vserver
EPSS score1.91%
Multiple race conditions in Linux-VServer 1.22 with Linux kernel 2.4.23 and SMP allow local users to cause a denial of service (kernel oops) via unknown attack vectors related to the (1) s_info and (2) ip_info data structures and the (a) forget_original_parent, (b) goodness, (c) schedule, (d) update_process_times, and (e) vc_new_s_context functions.CVE-2005-0178linuxlinux_kernel+2EPSS score0.36%
Race condition in the setsid function in Linux before 2.6.8.1 allows local users to cause a denial of service (crash) and possibly access portions of kernel memory, related to TTY changes, locking, and semaphores.CVE-2005-4418vserverutil-vserverEPSS score1.82%
util-vserver before 0.30.208-1 with kernel-patch-vserver before 1.9.5.5 and 2.x before 2.3 for Debian GNU/Linux sets a default policy that trusts unknown capabilities, which could allow local users to conduct unauthorized activities.CVE-2004-2613vserverlinux-vserverEPSS score2.45%
Unspecified vulnerability in procfs in the Linux-VServer stable branch for the 2.4 kernel before 1.23 and Linux-VServer development branch for the 2.4 kernel before 1.3.5 has unspecified impact and attack vectors, related to "write access to specific proc entries from a vserver context", a different vulnerability than CVE-2004-2408.CVE-2004-2408vserverlinux-vserverEPSS score0.37%
Linux VServer 1.27 and earlier, 1.3.9 and earlier, and 1.9.1 and earlier shares /proc permissions across all virtual and host servers, which allows local users with the ability to set permissions in /proc to obtain system information or cause a denial of service on other virtual servers or the host server.CVE-2006-1656debianutil-vserver+1EPSS score0.36%
vserver in util-vserver 0.30.209 executes a command as root when the suexec userid parameter is invalid and non-numeric, which might cause local users to inadvertently execute dangerous commands as root.