Vcenter Chargeback ManagerApplication · VMware
CVE-2013-3520
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 · uneditedVMware vCenter Chargeback Manager (aka CBM) before 2.5.1 does not proper handle uploads, which allows remote attackers to execute arbitrary code via unspecified vectors.
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 confidenceVMware vCenter Chargeback Manager before version 2.5.1 contains an improper file upload handling vulnerability that allows remote unauthenticated attackers to upload and execute arbitrary code on the affected system. This is a critical file upload vulnerability leading to remote code execution (RCE).
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 Chargeback ManagerApplication
<= 2.5.0= 1.5.0= 1.6.0= 1.6.1= 1.6.2= 2.0.0= 2.0.1CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if VMware vCenter Chargeback Manager is installedCheck for the CBM web interface by accessing the URL typically at https://<server>/cbm/ or look for the 'VMware vCenter Chargeback Manager' service running on the systemAffected if The CBM web interface is accessible and the service is running on the system
-
Determine the installed version of vCenter Chargeback ManagerLog into the CBM web interface and navigate to the 'About' or 'Help' section to view the version, or check the installer logs and configuration files in the CBM installation directoryAffected if The version displayed is 1.5.0, 1.6.0, 1.6.1, 1.6.2, 2.0.0, 2.0.1, or any version up to and including 2.5.0
-
Verify if the file upload functionality is enabledCheck if the CBM upload endpoint is accessible without authentication by attempting to access the file upload mechanism in the CBM administrative interfaceAffected if The file upload functionality is exposed and accessible without authentication
The system is affected if VMware vCenter Chargeback Manager is running with a version between 1.5.0 and 2.5.0 inclusive, and the file upload interface is accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade VMware vCenter Chargeback Manager to version 2.5.1 or later to remediate this vulnerability. If immediate upgrade is not feasible, implement network access controls to restrict exposure of the CBM interface to trusted networks only.
Fix this in Vcenter Chargeback Manager
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-3520 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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