# CVE-2009-2856: Information disclosure in n/a

> Remote attackers can sniff cleartext VDI configuration data from LDAP sessions when anonymous binding is enabled in Sun VDI.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cp92-4h8q-cwwj

## What is CVE-2009-2856?

CVE-2009-2856 is a low-severity vulnerability in n/a, published on 18 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sun Virtual Desktop Infrastructure (VDI) 3.0, when anonymous binding is enabled, does not properly handle a client's attempt to establish an authenticated and encrypted connection, which might allow remote attackers to read cleartext VDI configuration-data requests by sniffing LDAP sessions on the network.

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

## Which versions are affected by CVE-2009-2856?

It affects 1 product.


Products: Sun Virtual Desktop Infrastructure.

## How do I fix CVE-2009-2856?

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

## Is CVE-2009-2856 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3923](https://insights.sbomify.com/CVE-2009-3923/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2856 and fix it if it is affected.

What it is: CVE-2009-2856 is a low-severity vulnerability in n/a, published on 18 Aug 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-2856 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-2009-2856/ (Markdown: https://insights.sbomify.com/CVE-2009-2856/index.md)
```

## Sources

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

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