# CVE-2005-4412: Information disclosure in n/a

> Attackers with local session access can retrieve cached plaintext passwords from the Citrix Program Neighborhood client GUI.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4rx4-97jg-645p

## What is CVE-2005-4412?

CVE-2005-4412 is a low-severity vulnerability in n/a, published on 20 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Citrix Program Neighborhood client before 9.150 caches the user password in plaintext in the GUI while asterisks are used to visually obfuscate the password, which allows attackers with access to the session to obtain the password by using a tool to directly access the field.

## Which versions are affected by CVE-2005-4412?

It affects 1 product.


Products: Citrix Program Neighborhood Client.

## How do I fix CVE-2005-4412?

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

## Is CVE-2005-4412 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4412 and fix it if it is affected.

What it is: CVE-2005-4412 is a low-severity vulnerability in n/a, published on 20 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4412 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-2005-4412/ (Markdown: https://insights.sbomify.com/CVE-2005-4412/index.md)
```

## Sources

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

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