# CVE-2013-3520: Code injection in n/a

> Remote attackers can execute arbitrary code on VMware vCenter Chargeback Manager due to improper handling of uploads.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g5m4-7cmw-qxm9

## What is CVE-2013-3520?

CVE-2013-3520 is a high-severity code injection vulnerability in n/a, published on 17 Jun 2013. It can be exploited over the network, with no action from the victim.

### Official description

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

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2013-3520?

It affects 1 product.


Products: Vmware Vcenter Chargeback Manager.

## How do I fix CVE-2013-3520?

No fix has been published for CVE-2013-3520 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-3520 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3520 exists.

Public exploit code:

- VMware vCenter Chargeback Manager ImageUploadServlet Arbitrary File Upload (metasploit)
- VMware vCenter - Chargeback Manager ImageUploadServlet Arbitrary File Upload (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-1472](https://insights.sbomify.com/CVE-2012-1472/): XML external entity in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3520 and fix it if it is affected.

What it is: CVE-2013-3520 is a high-severity code injection vulnerability in n/a, published on 17 Jun 2013. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-3520 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-3520/ (Markdown: https://insights.sbomify.com/CVE-2013-3520/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-3520
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-3520
- OSV: https://osv.dev/vulnerability/CVE-2013-3520

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-3520/
Summaries are generated and may contain mistakes; the official description above is the record.