# CVE-2012-1513: Information disclosure in n/a

> Remote authenticated administrators can obtain sensitive vCenter Server passwords by reading an HTML document in the Web Configuration tool.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pv9q-9grm-74mr

## What is CVE-2012-1513?

CVE-2012-1513 is a medium-severity vulnerability in n/a, published on 16 Mar 2012. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Web Configuration tool in VMware vCenter Orchestrator (vCO) 4.0 before Update 4, 4.1 before Update 2, and 4.2 before Update 1 places the vCenter Server password in an HTML document, which allows remote authenticated administrators to obtain sensitive information by reading this document.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Vmware Vcenter Orchestrator.

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

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

## Is CVE-2012-1513 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-6934](https://insights.sbomify.com/CVE-2015-6934/): Deserialization in n/a (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1513 is a medium-severity vulnerability in n/a, published on 16 Mar 2012. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-1513 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-1513/ (Markdown: https://insights.sbomify.com/CVE-2012-1513/index.md)
```

## Sources

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

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