# CVE-2012-1472: XML external entity in n/a

> Remote attackers can read arbitrary files or cause denial of service in VMware vCenter Chargeback Manager via XML API requests.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 13 Mar 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-c25g-pf3j-289j

## What is CVE-2012-1472?

CVE-2012-1472 is a medium-severity vulnerability in n/a, published on 13 Mar 2012. It can be exploited over the network, with no action from the victim.

### Official description

VMware vCenter Chargeback Manager (aka CBM) before 2.0.1 does not properly handle XML API requests, which allows remote attackers to read arbitrary files or cause a denial of service via unspecified vectors.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-1472?

It affects 1 product.


Products: Vmware Vcenter Chargeback Manager.

## How do I fix CVE-2012-1472?

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

## Is CVE-2012-1472 being exploited?

There is no known exploitation of CVE-2012-1472 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-3520](https://insights.sbomify.com/CVE-2013-3520/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1472 and fix it if it is affected.

What it is: CVE-2012-1472 is a medium-severity vulnerability in n/a, published on 13 Mar 2012. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-1472 in the wild and no public exploit code.

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-2012-1472/ (Markdown: https://insights.sbomify.com/CVE-2012-1472/index.md)
```

## Sources

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

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