Vcenter vulnerabilitiesRanked by how likely they are to be used.

Product2 versions
The short answer

Vcenter is made by VMware. We track 5 published vulnerabilities listed under that exact name, across 2 versions. None of them is on the list of flaws known to be exploited today. VMware lists newer releases under their own names, such as vCenter Server, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Vcenter listed under other names? Yes.

VMware also lists Vcenter under more specific names, such as vCenter Server and Vcenter Server Appliance. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Vcenter vulnerabilities are being exploited?

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

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

Exploit likelihood

Which Vcenter 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. 4.6%

    The icmp_send function in net/ipv4/icmp.c in the Linux kernel before 2.6.25, when configured as a router with a REJECT route, does not properly manage the Protocol Independent Destination Cache (aka DST) in some...

    CVSS7.1Published12 Mar 2009
  2. 2.8%

    Multiple cross-site scripting (XSS) vulnerabilities in WebWorks Help 2.0 through 5.0 in VMware vCenter 4.0 before Update 1 Build 208156; VMware Server 2.0.2; VMware ESX 4.0; VMware Lab Manager 2.x; VMware vCenter Lab...

    CVSS4.3Published16 Dec 2009
  3. 2.1%

    Directory traversal vulnerability in vCenter Server in VMware vCenter 4.0 before Update 3 and 4.1 before Update 1, and VMware VirtualCenter 2.5 before Update 6a, allows remote attackers to read arbitrary files via...

    CVSS4.3Published9 May 2011
  4. 1.9%

    The self-extracting installer in the vSphere Client Installer package in VMware vCenter 4.0 before Update 3 and 4.1 before Update 1, VMware ESXi 4.x before 4.1 Update 1, and VMware ESX 4.x before 4.1 Update 1 does...

    CVSS5.0Published9 May 2011
  5. 0.4%

    vCenter Server in VMware vCenter 4.0 before Update 3 and 4.1 before Update 1 allows local users to discover the SOAP session ID via unspecified vectors.

    CVSS2.1Published9 May 2011
Precursor Intelligence

Running Vcenter? 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 →

We track 5 published vulnerabilities listed under the name Vcenter, across 2 versions.

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

VMware also lists Vcenter under more specific names, such as vCenter Server and Vcenter Server Appliance. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Vcenter. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.