# CVE-2008-3514: Information disclosure in n/a

> Remote attackers can enumerate valid user names in VMware VirtualCenter by exploiting client-side access control flaws, requiring an upgrade to secure the system.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2rrj-r6g7-f5gj

## What is CVE-2008-3514?

CVE-2008-3514 is a medium-severity vulnerability in n/a, published on 13 Aug 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

VMware VirtualCenter 2.5 before Update 2 and 2.0.2 before Update 5 relies on client-side "enabled/disabled functionality" for access control, which allows remote attackers to determine valid user names by enabling functionality in the GUI and then making an "attempt to assign permissions to other system users."

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

## Which versions are affected by CVE-2008-3514?

It affects 1 product.


Products: Vmware Virtualcenter.

## How do I fix CVE-2008-3514?

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

## Is CVE-2008-3514 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5990](https://insights.sbomify.com/CVE-2006-5990/): Security feature bypass in n/a (medium 4.0)
- [CVE-2008-4278](https://insights.sbomify.com/CVE-2008-4278/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3514 and fix it if it is affected.

What it is: CVE-2008-3514 is a medium-severity vulnerability in n/a, published on 13 Aug 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-3514 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-2008-3514/ (Markdown: https://insights.sbomify.com/CVE-2008-3514/index.md)
```

## Sources

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

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