PatchTheCVEvserver vulnerabilities
Recent CVEs affecting vserver products. 6 tracked.
vserver has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2006-04-06. Highest priority: CVE-2004-2613 (score 66/100).
- CVE-2006-1656 HIGH 7.2 UPGRADE vserver in util-vserver 0.30.209 executes a command as root when the suexec userid parameter is invalid and no
- CVE-2005-4418 HIGH 7.5 DOWNGRADE 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/Linu
- CVE-2005-0178 MEDIUM 6.2 DOWNGRADE DOWNGRADE Race condition in the setsid function in Linux before 2.6.8.1 allows local users to cause a denial of service
- CVE-2004-2613 HIGH 10.0 DOWNGRADE Unspecified vulnerability in procfs in the Linux-VServer stable branch for the 2.4 kernel before 1.23 and Linu
- CVE-2004-2408 LOW 3.6 DOWNGRADE Linux VServer 1.27 and earlier, 1.3.9 and earlier, and 1.9.1 and earlier shares /proc permissions across all v
- CVE-2003-1288 MEDIUM 5.0 DOWNGRADE Multiple race conditions in Linux-VServer 1.22 with Linux kernel 2.4.23 and SMP allow local users to cause a d
FAQ
How do I fix vserver vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is vserver being exploited right now?
None of the tracked vserver CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which vserver CVE should I patch first?
CVE-2004-2613 currently ranks highest (66/100): Unspecified vulnerability in procfs in the Linux-VServer stable branch for the 2.4 kernel before 1.23 and Linu.