Vserver vulnerabilitiesNone on the known-exploited list.

Vendor
The short answer

Vserver has 7 published vulnerabilities across 2 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Linux-Vserver, with 5. If you run Vserver software, patch the exploited flaws first.

See the exploited flaws

We keep watching the known-exploited list.

Products

Which Vserver products have the most vulnerabilities?

Linux-Vserver leads with 5 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. Linux-Vserver5
  2. Util-Vserver2
Published vulnerabilities
Known exploited

Which Vserver vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Vserver's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Vserver flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 3.1%

    Linux-VServer 1.24 allows local users with root privileges on a virtual server to gain access to the filesystem outside the virtual server via a modified chroot-again exploit using the chmod command.

    CVSS7.2Published6 Feb 2004
  2. 1.9%

    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...

    CVSS5.0Published31 Dec 2003
  3. 1.8%

    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...

    CVSS7.5Published31 Dec 2005
  4. 0.4%

    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...

    CVSS3.6Published31 Dec 2004
  5. 0.4%

    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.

    CVSS6.2Published7 Mar 2005
  6. 0.4%

    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.

    CVSS7.2Published6 Apr 2006
Every product

All Vserver products we track.

2 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

Precursor Intelligence

Running Vserver? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 7 published vulnerabilities across 2 products and 21 versions from Vserver.

None of Vserver's vulnerabilities is on the list of flaws known to be exploited today.

Linux-Vserver, with 5 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Vserver products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.