dbcve.org
Vcenter Server ApplianceApplication · VMware

CVE-2013-3080

HIGH · 9.0 CVSS v2.0 Published 2013-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
VMware vCenter Server Appliance (vCSA) 5.1 before Update 1 allows remote authenticated users to create or overwrite arbitrary files, and consequently execute arbitrary code or cause a denial of service, by leveraging Virtual Appliance Management Interface (VAMI) web-interface access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The VAMI web interface in VMware vCenter Server Appliance 5.1 before Update 1 contains an arbitrary file write vulnerability. Authenticated remote attackers can leverage this flaw to create or overwrite any file on the system, enabling arbitrary code execution or denial of service conditions.

MitigationApply VMware vCSA 5.1 Update 1 or later to patch the vulnerability. Alternatively, restrict access to the VAMI web interface to trusted administrators only until patching can be completed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vcenter Server ApplianceApplication
Affected:= 5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm vCenter Server Appliance is installed
    Identify if the target system is running VMware vCenter Server Appliance (vCSA). Check system inventory, running services, or login to the vCSA management interface.
    Affected if The system is not VMware vCenter Server Appliance (this CVE does not apply).
  2. Check installed vCSA version
    Access the vCSA admin interface or use command line (e.g., 'vmware -v' or check /etc/vmware-vcsa/version') to determine the exact installed version.
    Affected if Version is not exactly 5.1 (versions other than 5.1 are not affected by this specific CVE).
  3. Determine if Update 1 is applied
    Check if VMware vCSA 5.1 Update 1 has been installed. Review patch level via the VAMI interface (port 5480) or check system documentation for patch history.
    Affected if The system runs vCSA 5.1 without Update 1 or later patches applied.
  4. Verify VAMI web interface accessibility
    Confirm the VAMI web interface (typically on port 5480) is network-accessible. Check firewall rules, exposed ports, and whether the service is running.
    Affected if VAMI interface is exposed to untrusted networks (authenticated attackers require access to exploit this flaw).

The environment is affected if running vCSA version 5.1 without Update 1 applied and the VAMI web interface is accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply VMware vCSA 5.1 Update 1 or later to patch the vulnerability. Alternatively, restrict access to the VAMI web interface to trusted administrators only until patching can be completed.

Recommended fix High confidence

vCenter Server Appliance 5.1 Update 1 or later

  1. Verify current vCSA version by accessing the VAMI web interface at https://<appliance_ip>:5480
  2. Download VMware vCenter Server Appliance 5.1 Update 1 from VMware's official download portal
  3. Back up the vCSA configuration and any critical data
  4. Apply the update through the VAMI web interface by selecting 'Check for Updates' and following the upgrade wizard, or by mounting the ISO and running the installer
Caveat Test the upgrade in a non-production environment first; ensure compatibility with vSphere infrastructure components before applying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vcenter Server Appliance Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-3080 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data